I've disabled most of my logrotate stuff, and I rotate my logs with awstats. I also disabled log rotation for mysql.
The "answer" would be to SUID logrotated. I have NO IDEA what the security implications of that are. TTYS Lloyd At 10:02 AM 9/27/2002 +0100, you wrote: >Hi all, > >I have just realised what caused my Apache problems earlier. >logrotate was being run as root from /etc/cron.daily/ and once it had >rotated the apache log it was recreating one as root (which Apache >then couldn't write to). > >So, how do I overcome this problem? > >Also, I have realised that it it a security risk to allow the admin to >edit the logrotate config files (or /etc/logrotate.d/) when it is >running as root (they could persuade logrotate to remove a 'log' file >from the skel!) Anyone got any ideas? > >I suppose I could setup separate logrotate cron jobs for the admin, >web and root user (no editing root users) but it seems a bit messy. >Is this the only solution? > >Kind Regards, > >-- >Ben Kennish >[EMAIL PROTECTED] > >------------------------- The freeVSD Support List -------------------------- >Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support >Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support >Archives: http://freevsd.org/support/mail-archives/freevsd-support >----------------------------------------------------------------------------- Discovery consists of seeing what everybody has seen and thinking what nobody has thought. -- Albert Szent-Gyorgyi (1893-1986) ------------------------- The freeVSD Support List -------------------------- Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support Archives: http://freevsd.org/support/mail-archives/freevsd-support -----------------------------------------------------------------------------
