Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I would think you would want to set up a system so that normal users can only change files and directories where they are the owner. If it is set up that way, then why would you care how a user changed something?
If you're talking about a mounted directory, it can change permissions based on WHO mounted it. Having a more explicit /etc/fstab entry might tame that beast. Otherwise your system might be a bit hosed.
Otherwise fam or gam_server might help ID something. Or just change chmod / chgrp / chown to include some sort of logging. You might also check ~/.bash_history to see who's being naughty for each user. moot if they can log in as root. But there might be some /var/log/ stuff to indicate who's been doing that as well. Depending on how your system is setup.
If it's a device (/dev/), udev might be handling those perms at creation time. Any changes made to the /dev/ after boot are likely lost at the next boot.
OK, I maybe didn't explain myself very well. I do not have root. I was trying to help someone find out who changed permissions on an entire dir tree. I didn't set it up, nor can I change the set up. I DO NOT have root. I don't have a uid either. So, we have someone or a script which is what I think it is that is changing a dir tree from 777 to 755 which screws up the night scripts. I was wondering if anyone knew besides something like tripwire ( something free ) that would tell me who or what did that.
gam_server is the next gen of that. Whatever that is. If you don't have root, even if you ID what's causing it, you probably can't change it. What file system is this tree on? Some file systems can have alternate perms. Cron is probably a good place to check. It could also be the selinux stuff. If it's not a custom thing, then you might not be the only one with the problem. If it goes with some other action (reboot) / cron job or something. There might be a timestamp on the tree to hint at when it happens, if it's consistent (every day +/- 5 minutes) then it's probably automated, i.e. cron (or any number of other alternatives). I don't know of any humans that consistent.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.