Hypothesis:
When logrotate rotates away log files, your cron job has to create a new
log file. This new log file apparently gets the default (for root cron
jobs) permission of 600.
A solution: have your cron job change the permission of your log file
each time it writes; or before writing it is to check if the logfile
exists. If the logfile didn't exist prior to this cron job run, then
after writing (creating) the logfile, change its permission to 644.
--- Omer
WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html
On Thu, 19 Dec 2002, 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.
>
> 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.
=================================================================
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]
