On Friday 01 September 2006 02:11, Craig Millar wrote:
On 31/08/06 17:17 +0200, stephan beal wrote:
On Thursday 31 August 2006 11:27, Craig Millar wrote:
open("/bin/date", O_RDONLY) ? ? ? ? ? ? = -1 EPERM (Operation not permitted)
??? Can't read it? That sounds very suspect.
Suspect? Should I be fearing a knock on the door from the authorities? ;-) Do you have any idea why it might be this way?
i can't even begin to think of why unless the permissions on your system files have been hosed somehow. stephan@owl:/lib> l ld-linux.so.2 lrwxrwxrwx 1 root root 9 2006-06-21 14:29 ld-linux.so.2 -> ld-2.4.so stephan@owl:/lib> l ld-2* -rwxr-xr-x 1 root root 124463 2006-05-07 20:26 ld-2.4.so
man 2 open: ... EPERM The O_NOATIME flag was specified, but the effective user ID of the caller did not match the owner of the file and the caller was not privileged (CAP_FOWNER).
Though i don't quite believe that the ATIME is the only reason an EPERM error is signaled.
Assuming this was the case, any idea how I could resolve it? Sorry so many questions, I've been unable to find any other constructive information on this matter. My google-fu has deserted me in my time of need.
You can try mounting / with with the 'noatime' option (add it to your /etc/fstab), but i would be surprised if you really need this. It would be a kludgy workaround, at best. man mount: ... noatime Do not update inode access times on this file system (e.g, for faster access on the news spool to speed up news servers). The theory being, if EPERM really is caused by the O_NOATIME flag, that turning of atime updates for that filesystem might work around the problem. Aside from that, i'm clueless as to what might cause this. -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts