It is just logrotate doing its job.  After moving the log file, logrotate must restart 
syslogd for it to create a new log file.

Bill


> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Tib
> Sent: Sunday, November 12, 2000 9:37 PM
> To: [EMAIL PROTECTED]
> Subject: [expert] syslog problems
> 
> 
> Recently I left a 'tail -f' on a few log files going and saw 
> some interesting
> output. Can someone explain this and possibly how to fix it? 
> I'm stumped why
> syslogd would restart 10 times in the space of three seconds. Anyone?
> 
> ----- from the messages file -----
> Nov 12 04:02:11 unica syslogd 1.3-3: restart.
> Nov 12 04:02:11 unica syslogd 1.3-3: restart.
> Nov 12 04:02:13 unica syslogd 1.3-3: restart.
> Nov 12 04:02:13 unica syslogd 1.3-3: restart.
> Nov 12 04:02:13 unica syslogd 1.3-3: restart.
> Nov 12 04:02:13 unica syslogd 1.3-3: restart.
> Nov 12 04:02:14 unica syslogd 1.3-3: restart.
> Nov 12 04:02:14 unica syslogd 1.3-3: restart.
> ----------------------------------
> 
> --------not sure which log--------
> [Sun Nov 12 04:06:41 2000] [warn] child process 23126 did not 
> exit, sending
> another SIGHUP
> [Sun Nov 12 04:06:41 2000] [warn] child process 23127 did not 
> exit, sending
> another SIGHUP
> [Sun Nov 12 04:06:42 2000] [warn] child process 22659 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22660 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22661 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22662 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22663 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22664 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22672 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22673 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22675 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22696 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22722 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22766 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22767 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 22768 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 1983 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 1985 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 1986 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 18627 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 23126 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:42 2000] [warn] child process 23127 still 
> did not exit,
> sending a SIGTERM
> [Sun Nov 12 04:06:47 2000] [notice] SIGHUP received.  
> Attempting to restart
> ------------------------------------
> 
> 
> 


Keep in touch with http://mandrakeforum.com: 
Subscribe the "[EMAIL PROTECTED]" mailing list.

Reply via email to