Hi folks, diffs of the original /etc/cron.daily/aaa_base show that what has been done to solve the problem described in the original question by Morten Christensen is wrong. What has been done involves doing a file copy instead of a file move followed by another cp /dev/null "$1" to make the size of the logfile zero. This might seem to work but has the effect that messages logged in the interval between the two cp's are lost. While not as bad as previously it is not the correct solution and examination of other files show that someone at SuSE already knows this.. I.e /etc/logfiles contains a 5th field that tells which service should be restarted - this is only used for apache but seems to be intended as a general solution. Since many logfiles are managed by syslogd syslogd might be restarted more than once but this is of minor concern a) because syslog will not loose messages by being restarted (by /etc/rc.d/syslog reload) and b) because this multiple restart will only happen if more than one logfile needs to be rotated which is unlikely. A complete fix of this problem requres examining all the mentioned in /etc/logfiles and adding which service should be restarted. I will leave that as an exercise for the reader (or perhaps someone at SuSE..) ;-) Best regards, \Gandalf -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/