On 01/09/06 04:48 +0200, stephan beal wrote:
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
Nope. Exactly the same here. md5sum for ld-2.4.so is also identical to my home machine which is working fine.
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.
This didn't work either, alas.
Aside from that, i'm clueless as to what might cause this.
Makes two of us! Thanks for your time anyways. Best Craig