On Thu, 2002-12-19 at 18:19, shlomo solomon wrote: > > The problem is that every so often (I don't know when it happens), the > permission becomes 600 and non-root users can no longer read the file. There > are also some gz files in the /var/log/mylogs directory (created by > logrotate). The same thing happens to their permissions too.
I bet that logrotate is the one to blame for this. It simply creates the files with it's default permissions. Check logrotate config file for the dirty details. > > My solution was simple - run a cron job to reset the permissions for all files > in the directory to 644. But, although that works, it seems strange that > **something** is changing the permissions back to 600. > > Any ideas? - TIA If you can't find out what does it download Muli's syscall-tracker from syscalltrack.sf.net, install it and put a logging rule on all open() and chmod() syscalls on the system. This should tell you what does this ;-) Gilad. -- Gilad Ben-Yossef <[EMAIL PROTECTED]> http://benyossef.com Q: "What do you do if your Linux box goes down?" A: "Sit around in the dark until the power comes back on" ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
