similar to: Display warning when option doesn't have any effect?

Well, I screwed around a bit and after doing a "wbinfo -u" and a "wbinfo -g" I stopped getting the "unable to map SID" error. Now I'm getting a different error. ;-D [2004/05/25 09:09:34, 3] smbd/dosmode.c:unix_mode(111) unix_mode(FC2-i386-disc1.iso) returning 0744 [2004/05/25 09:09:34, 3] smbd/posix_acls.c:convert_canon_ace_to_posix_perms(2500)

https://bugzilla.samba.org/show_bug.cgi?id=6915 Summary: Reject passing an argument to an option that doesn't take one Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned at samba.org

I work on software that archives gigabytes of files to multiple sites. Occasionally one or two files have no read permissions: % ls -l dir/foo --w-------+ 1 abcserve myusers 11222 Jan 10 03:14 The error message is: rsync: send_files failed to open "/dir/foo" (in xxx): Permission denied (13) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at

https://bugzilla.samba.org/show_bug.cgi?id=11027 Bug ID: 11027 Summary: Sticky bit not set when using --chmod=D+t alone, without --perms Product: rsync Version: 3.0.9 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee:

We are using SAMBA 3.6.6 on Centos 5 with the acl_tdb VFS module. Our share is backed by storage on a SAN devices that does not support ACLs or extended attributes ... so we're trying the acl_tdb module as a mechanism to support Windows ACLs. We have verified that samba has ACL support enabled, and ACL support works find if we export the share from the local EXT4 filesystem. When trying to

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 other permissions. On 3/12/20 1:23 PM, Dimitrios Apostolou via rsync wrote: > 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:

Hello, I''ve modified tools/xenstore/xenstore_client.c to include a new utility, xenstore-chmod. This utility permits developers and administrators to manually change the permissions on arbitrary locations in XenStore from the command line. This is often helpful if you''re trying to debug an application that relies on XenStore and is encountering difficulties with permissions.

Hi there, I run the following code in R and got the warning like that, how can I change the memory.size? Or anything else? Thanks a lot! Faye temp<-apply(Idd4.perms$permstats[-stratum1,], + 2,sort) Error: cannot allocate vector of size 47.5 Mb In addition: Warning messages: 1: In apply(Idd4.perms$permstats[-stratum1, ], 2, sort) : Reached total allocation of 1023Mb: see help(memory.size)

Hi, Thanks for the note. How would explain the following snippet taken from `formals` doc page (the code comment is also from that doc) ? ## formals returns NULL for primitive functions. Use it in combination with ## args for this case. is.primitive(`+`) formals(`+`) formals(args(`+`)) Le sam. 6 oct. 2018 ? 13:42, Rui Barradas <ruipbarradas at sapo.pt> a ?crit :

https://bugzilla.samba.org/show_bug.cgi?id=9377 Summary: acls ignored when using neither --perms nor --chmod Product: rsync Version: 3.0.9 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chrysn at fsfe.org

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

I don't believe it is possible. I think the misunderstanding stems from the fact that the permissions are even stored in the xattr. They don't need to be there but they may as well be. They don't take much space. The real question would be when rsync reads the file to restore it and the file perms are different than the ones in the xattr which set does it use? On 3/16/20 10:01 AM,

There is more "fun" afoot here, but I don't recall what the point may be: > args(get("+")) function (e1, e2) NULL > args(get("[")) NULL > get("[") .Primitive("[") > get("+") function (e1, e2) .Primitive("+") The other index operators, "[[", "[<-", "[[<-" are similar The

Note that having "function" in its class attribute does not make an object a primitive. For example: > class(`[`) [1] "function" > is.primitive(`[`) [1] TRUE > class(`rnorm`) [1] "function" > is.primitive(`rnorm`) [1] FALSE Le dim. 7 oct. 2018 ? 10:04, Rui Barradas <ruipbarradas at sapo.pt> a ?crit : > Hello, > > I don't see why you

> On 7 Oct 2018, at 16:04 , Rui Barradas <ruipbarradas at sapo.pt> wrote: > > Hello, > > I don't see why you say that the documentation seems to be wrong: > > > class(args(`+`)) > #[1] "function" > > > args() on a primitive does return a closure. At least in this case it does. But in this case it doesn't: >

Hello, I don't see why you say that the documentation seems to be wrong: class(args(`+`)) #[1] "function" args() on a primitive does return a closure. At least in this case it does. Rui Barradas ?s 14:05 de 07/10/2018, Peter Dalgaard escreveu: > There is more "fun" afoot here, but I don't recall what the point may be: > >> args(get("+"))

The entries in xenstore have permission attributes. The attributes can be easily altered by xenstore-chmod, however, I cannot find a easy way to see them. I''ve modified xenstore_client.c to raise a new utility. The utility checks the permission and makes an easy-look output. Please tell me any suggestions. Thanks. Signed-off-by: Frank Pan <frankpzh@gmail.com> ---

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, rsync v3.0.7 I am backing up data to a USB memory drive that is formatted FAT32, which does not comprehend linux permissions. I added the "--no-perms" option to the option set. rsync still attempts to change the permissions. OPTS = "--no-perms --archive --stats --delete --itemize-changes - --quiet

Hello, I just upgraded from rsync 2.6.4 to 3.0.5 on Solaris 9 (sparc). Since then, I'm getting this error "cannot delete non-empty directory" on some directories. My command is: rsync -rltDvz --block-size=32768 --delete --delete-excluded --force --stats --perms=off --chmod=ug=rwX --chmod=o=rX --include "fchba/**" --exclude "*" $SQABASE/SQA/ $DESTBASE/SQA/

Hello, This is because args(`[`) returns NULL and class(NULL) is NULL. So the question would be why is the return value of args(`[`) NULL? Rui Barradas ?s 15:14 de 07/10/2018, Peter Dalgaard escreveu: > > >> On 7 Oct 2018, at 16:04 , Rui Barradas <ruipbarradas at sapo.pt> wrote: >> >> Hello, >> >> I don't see why you say that the documentation