Linux

I think you're looking at either a security issue or a flat-out employee goof-up over at the client's. Viruses are not the only thing that can eat data like Pac-man eats dots.

I probably would not have thought these unkind thoughts, except you yourself used the word 'suspicious'.

jeff s
spanish helpdesk technician

I can't comment on the Syrinex implementation of Linux but I run a server based on the Linux 2.0.36 kernel and one certainly can make changes on large numbers of files by running CHMOD recursively.

The other thought I had is that there is a default set of file permissions determined by the umask. If the umask got set to establish read-only permissions as the default, then all new files created after that point would be read-only.

My guess would be the ubitquitous "Operator Error". I know that as a Net Admin, I should be more paranoid and suspicious but I try not to attribute to malevolence that which was only ignorance. But I would want to re-visit the permissions and pay particular attention to the integrity of the root account.
paul

Paul M. Wright, Jr.
McKay Technologies

Partitions can be mounted read only as well. This is usually only if something goes horribly wrong, e.g. it fails to fsck and somebody deliberately mounts it to recover the data.

This is probably not your problem because you'd expect to see all sorts of horrible problems other than just "all the files are read only."

The most probable cause for this is someone using a chmod -R (recusive)by mistake, I would check everyone who has access to this .bash_history first to see if you can find evidence of this here. It is also possible that this has been done malicously, so if you find no evidence in .bash_history you may want to review your other system logs

This question was auto closed due to inactivity