Hi,
Max Nikulin wrote:
> Thomas, do you have in your collection of strange files a one moved out of a
> directory encrypted using fscrypt?
Not yet. I will have to think whether such files pose any particular
backup problem.
Have a nice day :)
Thomas
On 10/07/2024 08:48, Greg Wooledge wrote:
On Wed, Jul 10, 2024 at 08:20:23 +0700, Max Nikulin wrote:
On 10/07/2024 02:35, Thomas Schmitt wrote:
setfattr -n system.nfs4_acl -v
'\0\0\0\3\0\0\0\0\0\0\0\0\0\26\1\247\0\0\0\6OWNER@\0\0\0\0\0' /tmp/x
Shell does not interpret backslashes in sin
Hi,
Patrice Duroux wrote:
> $ getfattr -d test.sh
> $
One could get the impression that "system." attributes are kept obscure
by developers' intention.
I now found in the man page a few sentences which could be the origin of
my dim (and distorted) memories about this name space:
-m pattern, -
> So we now know how to prevent the immediate problem.
> Does "system.nfs4_acl" show up in
> getfattr -d test.sh
> ?
$ getfattr -d test.sh
$
And this is the same regardless the value (permissions or skip) for
system.nfs4_acl in /etc/xattr.conf
> Maybe it is the right package to learn more about
On the other hand, after modifying /etc/xattr.conf to replace:
system.nfs4_aclpermissions
by:
system.nfs4_aclskip
then test.sh works nicely:
$ ./test.sh
-rwxr-x--- 1 patrice patrice 300 Jul 9 10:46 ./test.sh
option: -p
exitcode: 0
-rwxr-x--- 1 patrice patrice 300 Jul 9 10:
Hi,
Patrice Duroux wrote:
> On the other hand, after modifying /etc/xattr.conf to replace:
> system.nfs4_aclpermissions
> by:
> system.nfs4_aclskip
> then test.sh works nicely:
So we now know how to prevent the immediate problem.
Does "system.nfs4_acl" show up in
getfa
Hi,
i wrote:
> > >setfattr -n system.nfs4_acl -v
> > > '\0\0\0\3\0\0\0\0\0\0\0\0\0\26\1\247\0\0\0\6OWNER@\0\0\0\0\0' /tmp/x
Max Nikulin wrote:
> Shell does not interpret backslashes in single (and double) quotes.
Non-interpretation by the shell was my intention. I wanted the string
to reach
On Wed, Jul 10, 2024 at 08:20:23 +0700, Max Nikulin wrote:
> On 10/07/2024 02:35, Thomas Schmitt wrote:
> > Here the error happens while trying to set the attribute.
> > Shell equivalent is
> >
> >setfattr -n system.nfs4_acl -v
> > '\0\0\0\3\0\0\0\0\0\0\0\0\0\26\1\247\0\0\0\6OWNER@\0\0\0\0\0'
On 10/07/2024 02:35, Thomas Schmitt wrote:
Here the error happens while trying to set the attribute.
Shell equivalent is
setfattr -n system.nfs4_acl -v
'\0\0\0\3\0\0\0\0\0\0\0\0\0\26\1\247\0\0\0\6OWNER@\0\0\0\0\0' /tmp/x
Shell does not interpret backslashes in single (and double) quotes.
Hi,
(I Cc: patrice.dur...@gmail.com because i see no "LDOSUBSCRIBER" in
the "X-Spam-Status:" header.)
Jumping ahead:
Look into the local file
/etc/xattr.conf
and try what happens if you change
system.nfs4_acl permissions
to
system.nfs4_acl s
> Looks like the error happens while trying to set the extended attributes
> on the destination file. I don't really know how xattr works, but
> it looks like it's trying to set an attribute named "system.nfs4_acl"
> on a file that's in the /tmp directory.
That is more clear to me now. And so I c
On Tue, Jul 09, 2024 at 19:12:28 +0200, Patrice Duroux wrote:
> $ LANG=C strace cp -p test.sh /tmp
[...]
> read(6, "# /etc/xattr.conf\n#\n# Format:\n# "..., 4096) = 681
> read(6, "", 4096) = 0
> close(6)= 0
> fgetxattr(4, "system.nfs4_acl", NULL
> If we can't figure it out from her replies to our *many* requests for
> additional information, then my next request would be to strace it,
> and see exactly which system call is failing.
$ LANG=C strace cp -p test.sh /tmp
execve("/usr/bin/cp", ["cp", "-p", "test.sh", "/tmp"], 0x7ffe58e09538 /*
Hi,
Patrice Duroux wrote:
> user:1234:-w-
So it's not that /tmp would refuse on ACL.
> getfacl : suppression du premier « / » des noms de chemins absolus
> (sorry for the french output)
The translator to french was not overly capricious. So my school french
suffices. Google would help if the t
Sorry for my direct answer.
-- Forwarded message -
De : Patrice Duroux
Date: mar. 9 juil. 2024 à 14:07
Subject: Re: question related to cp (-p) and /tmp
To: Thomas Schmitt
Hi Thomas,
Thanks!
Here is for the source file of the copy:
$ getfacl test.sh
# file: test.sh
# owner
On Tue, Jul 09, 2024 at 13:46:12 +0200, Thomas Schmitt wrote:
> Hi,
>
> Patrice Duroux wrote:
> > > cp: preserving permissions for '/tmp/test.sh': Operation not supported
>
> Greg Wooledge wrote:
> > I was thinking something similar, but the "ls -l ./test.sh" did not
> > show any markup indicatin
Hi,
Patrice Duroux wrote:
> > cp: preserving permissions for '/tmp/test.sh': Operation not supported
Greg Wooledge wrote:
> I was thinking something similar, but the "ls -l ./test.sh" did not
> show any markup indicating ACL.
At least cp calls ACL "permissions". See
https://sources.debian.org/
On Tue, Jul 09, 2024 at 13:20:04 +0200, Thomas Schmitt wrote:
> Patrice Duroux wrote:
> > option: --preserve=mode
> > cp: preserving permissions for '/tmp/test.sh': Operation not supported
> > exitcode: 1
> > [...]
> > It says that the operation is not supported but still the mode of the
> > copy i
Hi,
Patrice Duroux wrote:
> option: --preserve=mode
> cp: preserving permissions for '/tmp/test.sh': Operation not supported
> exitcode: 1
> [...]
> It says that the operation is not supported but still the mode of the
> copy is ok.
Maybe it sees ACL at the source file and your /tmp filesystem ca
On Tue, Jul 09, 2024 at 11:04:14 +0200, Patrice Duroux wrote:
> $ cat test.sh
> #!/usr/bin/sh
>
> export LANG=C
> ls -l ./test.sh
> echo "option: -p"
> cp -p ./test.sh /tmp
> echo "exitcode: "$?
> ls -l /tmp/test.sh
> rm /tmp/test.sh
> for p in mode timestamps ownership ; do
> echo "option: --pres
Hi,
On Sid (amd64), I am facing the following:
$ ./test.sh
-rwxr-x--- 1 patrice patrice 300 Jul 9 10:46 ./test.sh
option: -p
cp: preserving permissions for '/tmp/test.sh': Operation not supported
exitcode: 1
-rwxr-x--- 1 patrice patrice 300 Jul 9 10:46 /tmp/test.sh
option: --preserve=mode
cp: p
21 matches
Mail list logo
