similar to: xattrs: Permission denied?

Displaying 20 results from an estimated 300 matches similar to: "xattrs: Permission denied?"

2009 Jul 10
6
DO NOT REPLY [Bug 6546] New: lremovexattr problems
https://bugzilla.samba.org/show_bug.cgi?id=6546 Summary: lremovexattr problems Product: rsync Version: 3.0.6 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: Dave@Yost.com QAContact:
2007 Oct 17
0
xattrs on symlinks
As we all know, only osx supports xattrs on symlinks. Unfortunately, not only does osx support xattrs on symlinks, *every* symlink has, at the least, com.apple.FinderInfo. When backing up to a linux system, this results in one error message per symlink: rsync: rsync_xal_set: lsetxattr("User Guides And Information","user.com.apple.FinderInfo") failed: Operation not
2016 Dec 01
3
[PATCH v2 1/2] xattrs: Skip security.evm extended attribute
The security.evm extended attribute is fully owned by the Linux kernel and cannot be directly written from userspace. Therefore, we can always skip it. --- xattrs.c | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/xattrs.c b/xattrs.c index b105392..3b72e61 100644 --- a/xattrs.c +++ b/xattrs.c @@ -255,6 +255,9 @@ static int rsync_xal_get(const char *fname,
2007 Nov 15
2
rsync error?
Hi Folks Can anyone help me with the following error - is it serious; is the file transferred; are the other files transferred? [morgan@morgansmachine ~]$ rsync -a -X -A -z -v /home/morgan/Documents 192.168.1.30:/home/morgan/Documents morgan@192.168.1.30's password: building file list ... done rsync: rsync_xal_set:
2013 Apr 25
2
How are R version types named ? Any convention (like Hurricanes etc)
With reference to R News News: R version 3.0.0 (Masked Marvel) has been released on 2013-04-03. R version 2.15.3 (Security Blanket) has been released on 2013-03-01 R version 2.15.2 (Trick or Treat) .... R version 2.15.1 ("Roasted Marshmallows") ... R version 2.15.0 ("Easter Beagle") R version 2.14.0 ("Great Pumpkin") Dear R help List, How are these version types
2014 Feb 02
1
Bugg when using Extended Attributes flag -X
Hello, I found that using rsync on OS X can give some problems when it comes to Extended Attributes (-X flag). The server I use has Ubuntu with the filesystem XFS and I am trying to backup a OS X system to it. The problem is as far as I understand it that Linux Kernel has a liming on 64k f?r Extended Attributes and OS X don?t have this limit. Some error output. rsync: rsync_xal_set:
2015 Mar 11
2
Rsync ACLs over NFSv4 to EXT4 - rsync_xal_set: lsetxattr - Operation not supported
I think this is an NFS or ext4 question, but wanted to post this here for a sanity check. :) I've been searching for over a week for a solution and have turned up nil. I'm trying to rsync with options -AX over an NFSv4 mount TO an ext4 drive FROM an ext4 drive and both have acl and user_xattr enabled. The command: rsync -aAX /data/ /mnt/back/data results in: rsync:
2009 Apr 03
1
"Invalid argument (22)" & "Operation not supported (95)" ???
Hi Folks I've gone back over the list and the only reference I've found to "Invalid argument (22)" is here: http://lists.samba.org/archive/rsync/2006-May/015478.html That seems a different context of character set mismatches. The common parts to my errors are: rsync: rsync_xal_set: lsetxattr("...","security.selinux") failed: Invalid argument (22) And:
2008 Apr 14
0
[PATCH] xattrs not set on locked files that already exist on target
Working with rsync 3.0.2, it appears that rsync isn't unlocking files before setting the file attributes when those files already exist. This generates error messages on subsequent such as: rsync: rsync_xal_set: lsetxattr("locked_file","test_xattr") failed: Operation not permitted (1) rsync: rsync_xal_clear:
2007 Feb 09
1
[AAF] Determine matching field in a search result
I was wondering if it was possible to determine which field caused the match to occur (or contributed the most to the score) in a search result. For example, if I had a record { :name => ''pumpkin'', :age => -5, :address => ''Via Mandriola'' } and I did a search for ''Mandriola'', is it possible for acts_as_ferret to tell me that the
2015 Jan 08
4
unloadNamespace
In the documentation the closed thing I see to an explanation of this is that ?detach says "Unloading some namespaces has undesirable side effects" Can anyone explain why unloading tseries will load zoo? I don't think this behavior is specific to tseries, it's just an example. I realize one would not usually unload something that is not loaded, but I would expect it to do
2006 Apr 19
4
DO NOT REPLY [Bug 3701] New: rsync_xal_set: lsetxattr system.posix_acl_default failed: Permission denied
https://bugzilla.samba.org/show_bug.cgi?id=3701 Summary: rsync_xal_set: lsetxattr system.posix_acl_default failed: Permission denied Product: rsync Version: 2.6.7 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:
2007 Mar 08
3
[BUG] clear ACL-s on destination
Destroy ACL-s on destination when no ACL-s differens between source and destination. Bug is somehow related with function send_file_name() called with negative file descriptor f. There is no such bug in 2.6.9 version, but there options "-X -A --deleted" can't be used (we have "Internal error: wrong write used in receiver."). If I fix this, avoid calling send_acl() &
2023 Oct 31
5
NUT v2.8.1 is released
...it was almost midnight, Cinderella became a pumpkin, and NUT was released!.. Trick or treat?! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20231031/f3590340/attachment.htm>
2023 Oct 31
5
NUT v2.8.1 is released
...it was almost midnight, Cinderella became a pumpkin, and NUT was released!.. Trick or treat?! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20231031/f3590340/attachment.htm>
2008 Jun 25
2
DO NOT REPLY [Bug 5565] New: xattrs not set on locked files that already exist on target
https://bugzilla.samba.org/show_bug.cgi?id=5565 Summary: xattrs not set on locked files that already exist on target Product: rsync Version: 3.0.3 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org
2017 Mar 15
1
Error: memory exhausted (limit reached?)
Hi, I first posted this message on r-help, but got redirected here. I encounter a strange memory error, and I'd like some help to determine if I'm doing something wrong or if there's a bug in recent R versions... I'm currently working on a DeepNet project @home, with an old PC with 4Gb RAM, running Ubuntu 16.04. For efficiency reason, I preprocessed my dataset and stored it as
2017 Jan 18
3
Taking determinant of a matrix of NAs results in intermittent memory corruption
Greetings; I've posted the following to R's bug tracking system (at https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17210 ) and Martin Maechler requested that I post to this list as well. If I start R from the command line with --vanilla, then repeatedly execute the following line: det(matrix(nrow=10,ncol=10)) ... I eventually get a crash, with error: *** Error in
2007 Oct 30
1
Rsync 3.0.0pre4 errors with ACLs and Xattrs between OSX and Linux
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's my understanding that as of 3.0 rsync supports OS X ACLs and extended attributes, and that it should be possible to backup a tree from an OS X system that contains files and folders with ACLs and extended attributes to a Linux host filesystem that has both "user_xattrs" and "acl" enabled on the destination file system.
2009 Oct 28
1
Operation not supported (95)
Hi guys, I'm running into a problem that I'm sure which part of the process fails. I use wget (OSX Leopard, wget 3.0.6 compiled from source) to backup my ~/Pictures directory to a linux server, also with wget 3.0.6 (Debian). In persuit of being sure I get everything from HFS filesystem (resource fork/metadata), I'm getting the following error: rsync: rsync_xal_set: