similar to: Samba and LinuxMDK 9 file perms oddities?

I'm setting up quota for my users, my users have a UID starting on >5000 and GID = 5000, and when I query the quota, for example in IMAP, I get: Nov 8 14:13:28 fastmail dovecot: imap-login: Login: user=<a at a.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=18660, secured, session=<uByciFkH2gB/AAAB> Nov 8 14:13:37 fastmail dovecot: imap(a at a.com): Error:

rsync --perms -M--fake-super src dst For me, this command means that rsync should save the original perms in the xattr, and leave the real file mode to the umask default. Currently it also modifies the real file mode, and there is no way to store something different in the xattr. According to an old bug report that I found, more people would like --fake-super to be a complete attribute

Thank you for the feedback, I'm glad to see that different people see the issue differently. As a followup question, what would you expect this to do: rsync --perms --chmod g+rX -M--fake-super src dst I would expect it to store the original permissions in the xattr, while modifying the real file mode according to the chmod. On Thursday, March 12, 2020 6:06:34 PM CET, Kevin Korb via rsync

On Mon, 2014-03-17 at 14:25 +1030, Rusty Russell wrote: > Erk, our tests are insufficient. Testbuilding an allmodconfig with this > now: Good idea. > diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h [] > @@ -188,6 +188,9 @@ struct kparam_array > /* Default value instead of permissions? */ \ > static int __param_perm_check_##name

On Mon, 2014-03-17 at 14:25 +1030, Rusty Russell wrote: > Erk, our tests are insufficient. Testbuilding an allmodconfig with this > now: Good idea. > diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h [] > @@ -188,6 +188,9 @@ struct kparam_array > /* Default value instead of permissions? */ \ > static int __param_perm_check_##name

Thanks. This is a bit counter-intuitive to me. So how would you tell rsync to store the original permissions in the xattr, but do not touch the real file mode? On Thursday, March 12, 2020 6:26:18 PM CET, Kevin Korb via rsync wrote: > I would expect that the sending rsync would only send the perms provided > modified by the --chmod. I wouldn't expect the receiver to even know > the

Joe Perches <joe at perches.com> writes: > On Sun, 2014-03-16 at 22:00 -0700, Joe Perches wrote: >> On Mon, 2014-03-17 at 14:25 +1030, Rusty Russell wrote: >> >> > Erk, our tests are insufficient. Testbuilding an allmodconfig with this >> > now: >> >> Good idea. >> >> > diff --git a/include/linux/moduleparam.h

Joe Perches <joe at perches.com> writes: > On Sun, 2014-03-16 at 22:00 -0700, Joe Perches wrote: >> On Mon, 2014-03-17 at 14:25 +1030, Rusty Russell wrote: >> >> > Erk, our tests are insufficient. Testbuilding an allmodconfig with this >> > now: >> >> Good idea. >> >> > diff --git a/include/linux/moduleparam.h

The firewall didnt help matters. I think its FUBAR and I need to reformat anyways, so ill reformat and reinstall and put fresh SAMBA up, on Mandrake 9.0. The system has 2 NICs and NET_MASQ shares internet to the XP machine. Therein it acts as a DHCP server and has a firewall. I will open 139 from the start next time.

On Fri, Mar 14, 2014 at 10:38:40AM -0700, Joe Perches wrote: > > +static int queue_depth = 64; > > +module_param(queue_depth, int, 444); > > 444? Really Ted? Oops, *blush*. Thanks for catching that. - Ted

On Fri, Mar 14, 2014 at 10:38:40AM -0700, Joe Perches wrote: > > +static int queue_depth = 64; > > +module_param(queue_depth, int, 444); > > 444? Really Ted? Oops, *blush*. Thanks for catching that. - Ted

I have a share which a group write list. That group is mapped to a Linux group in /etc/group. That group in Linux has two users. The first user listed is suddenly unable to write, but the second one is. With the affected user logged in to Win2K, ifmember /list shows they are a member of the group, as does the working account. I am guessing one of those .tdb files or something got scrambled on the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 on dovecot launch, 'dovecot.log' is created as: -rw------- 1 root testuser 271 2006-09-11 07:58 dovecot.log which causes an apparent perms prob with exim using dovecot's LDA ... what/how do i define/change the LOG's ownership/perms with? it seems to ignore the dovecot.conf umask setting, etc. thx. richard - -- /"\ \

Using --existing, I would like to transfer files created by root to home dirs, where the files would be updated, but leave the user,group and perms as they were. ie root creates a new file on the sending system, rsyncs it to the home dir of the user, leaving the perms untouched. Seems there is no option for this - the users are not defined on the sending system. I cant do it backwards due to

kio_smb (smb:// in Konqueror) stopped working, and I tracked it down to a broken smbclient With samba-2.2.6pre CVS (from 20020824) [bgmilne@bgmilne bgmilne]$ smbclient //atlas/QMuzik added interface ip=xxx.xxx.xxx.36 bcast=xxx.xxx.xxx.255 nmask=255.255.255.0 session request to ATLAS failed (SUCCESS - 0) session request to *SMBSERVER failed (SUCCESS - 0) [bgmilne@bgmilne bgmilne]$ smbclient

My original thread had the incorrect subject line. The original trouble / question remains open and unsolved. Greetings- I am working through coming up with a Linux client integration to Samba PDC's. I mount several shares with this sort of syntax: /bin/mount -t cifs -o credentials=/home/userid/.smbcredentials,uid=userid,gid=userid,dmask=0777,fmask=0666 //ldslnx01/data /mnt/ldslnx01/data/

Greetings- I am working through coming up with a Linux client integration to Samba PDC's. I mount several shares with this sort of syntax: /bin/mount -t cifs -o credentials=/home/userid/.smbcredentials,uid=userid,gid=userid,dmask=0777,fmask=0666 //ldslnx01/data /mnt/ldslnx01/data/ However when I create new files/dirs on the Samba share from the Linux workstation, the perms are not 0666/0777

I did yum update the other day and it downloaded and installed a bunch of stuff, including a kernel. Didn't have time to reboot until today. today when I reboot, I get a message something like this during boot (from memory since it doesn't seem to be saved in dmesg anywhere): CRITICAL unknown class console at line 23 in /etc/security/console.perms and when the system finishes booting,

Couple more bikesheddy things: Is there ever a reason to use a non __builtin_const_p(perms)? Maybe that should be a BUILD_BUG_ON too BUILD_BUG_ON(!builtin_const_p_perms) My brain of little size gets confused by the BUILD_BUG_ON_ZERO(foo) + vs BUILD_BUG_ON(foo); as it just seems like more text for the same content. Is there any value on the "_ZERO(foo) +" I don't understand?

Couple more bikesheddy things: Is there ever a reason to use a non __builtin_const_p(perms)? Maybe that should be a BUILD_BUG_ON too BUILD_BUG_ON(!builtin_const_p_perms) My brain of little size gets confused by the BUILD_BUG_ON_ZERO(foo) + vs BUILD_BUG_ON(foo); as it just seems like more text for the same content. Is there any value on the "_ZERO(foo) +" I don't understand?