Re: permissions all zero when using 'cp'
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
it gets weirder ...
mlo@X:/tmp$ ( env -i; LANG=C lsattr; )
- ------------------- ./test
- ------------------- ./ssh-IxYCtP5517
- ------------------- ./strace1
lsattr: Permission denied While reading flags on ./test.bak
- ------------------- ./strace2
- ------------------- ./test.bak2
lsattr: Permission denied While reading flags on
./reportbug-base-20101229-15630-9rIBOP
- ------------------- ./cp.strace.out
root@X:/tmp# ( env -i; LANG=C lsattr; )
- ------------------- ./test
- ------------------- ./ssh-IxYCtP5517
- ------------------- ./strace1
- ------------------- ./test.bak
- ------------------- ./strace2
- ------------------- ./test.bak2
- ------------------- ./reportbug-base-20101229-15630-9rIBOP
- ------------------- ./cp.strace.out
root@X:/tmp# ls -altr
insgesamt 44
drwxrwxrwt 2 root root 4096 29. Dez 15:06 .X11-unix
drwxrwxrwt 2 root root 4096 29. Dez 15:06 .ICE-unix
- -rw-rw-r-- 1 root root 0 29. Dez 21:47 test.bak2
- -rw-rw-r-- 1 root root 0 29. Dez 21:47 test
drwxr-xr-x 21 root root 4096 29. Dez 22:06 ..
- ---------- 1 root root 0 29. Dez 22:22 test.bak
- -rwsr-Sr-T 1 root root 6449 29. Dez 22:22 strace1
- -rwsr-Sr-T 1 root root 6864 29. Dez 22:22 strace2
- --wx--s--T 1 root root 419 29. Dez 22:37
reportbug-base-20101229-15630-9rIBOP
- -rw-r--r-- 1 root root 2139 30. Dez 20:23 cp.strace.out
drwx------ 2 mlo users 4096 31. Dez 10:48 ssh-IxYCtP5517
drwxrwxrwt 5 root root 4096 31. Dez 10:50 .
Am 30.12.2010 21:03, schrieb Bob Proulx:
> Martin Lorenz wrote:
>> mlo@X:~$ type cp
>> cp is aliased to `cp -i'
>>
>> as root:
>>
>> root@X:~# type cp
>> cp is /bin/cp
>
> It looks okay. I was hoping that it pointed to a different command
> that could be traced to a problem. But apparently not.
>
>>> Try running in a clean environment to see if it is an environment
>>> variable. 'env -i' will initialize an empty environment.
>
> It looks okay. I was hoping that an environment variable such as
> LD_PRELOAD or LD_LIBRARY_PATH would have pointed to a rogue library.
> Without that in the environment it would work. But apparently not.
>
> Those two ideas were my best guesses at what could cause such strange
> behavior. Unfortunately your reply information does not show anything
> wrong that I can see in either of those two cases.
>
>>> If that still shows a problem then look deeper with strace.
>>> $ strace -v -e trace=file -o /tmp/cp.strace.out cp testfile1 testfile2
>> open("testfile1", O_RDONLY|O_LARGEFILE) = 3
>> open("testfile2", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0) = 4
>
> That is perfectly normal for a 32-bit system. Okay.
>
>> does this tell you something?
>
> Unfortunately your information looked normal and did not point me
> toward anything that looked like a problem.
>
> Mike Bird's guess at selinux was a good question.
>
> I am not conversationally fluent with filesystem attributes. Is it
> possible that 'chattr' was run on your filesystem? Try running
> 'lsattr' and listing the filesystem attributes to see if something has
> been set. You will need to read the documentation for information as
> I know little about it but only that they exist. For me I only see
> dashes on my filesystem because I have not set any attributes.
>
> lsattr
>
> Sorry but I do not know. I have exhausted my guesses.
>
> Bob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNHafzAAoJECZ8myNlGwU1ansH/j2pQzPNHkRU17ro8UETyVlb
RLPxWcuToxF61NJrvpdt7EVtTUC13EAGv07N+aMqaSs2xOcmgGHUVclJDp+tlPum
ckjKIXr0PR0mnDyVKV8Oa0jKqgII9o6zx3UjDrjdmI3cHMMCUOJb/XBu0WHy4smn
7cK4Z+wtG0TzzGR0mWh7MKl2J2bxfGOOYYT34er79CiFZ2W/CQzpq44Ln3snvDFF
0ygxO7Ag1B9OkGL6+aWjYXuqsFCJuoXrrPzH09dsGUDFqMNVU9pdXr/s/pXOwsU5
5S/8H3pEBb40FgJzxlghCNx598LjOOhHE1P0L82vxVcoAV4WI1iTS+3HmtmwF3w=
=Goqp
-----END PGP SIGNATURE-----
Reply to: