For those who asked about starting syslog-ng on boot, here is what I did for Solaris 8. I simply modified the /etc/rc2.d/S74syslog script: case "$1" in 'start') if [ -f /etc/syslog-ng/syslog-ng.conf -a -f /usr/sbin/syslog-ng ]; then echo 'syslog-ng service starting.' # # Before syslogd starts, save any messages from previous # crash dumps so that messages appear in chronological order. # /usr/bin/savecore -m if [ -r /etc/dumpadm.conf ]; then . /etc/dumpadm.conf [ "x$DUMPADM_DEVICE" != xswap ] && \ /usr/bin/savecore -m -f $DUMPADM_DEVICE fi if [ ! -f /var/adm/messages ]; then /usr/bin/cp /dev/null /var/adm/messages /usr/bin/chmod 0644 /var/adm/messages fi /usr/sbin/syslog-ng >/dev/msglog 2>&1 & fi ;; 'stop') echo 'syslog-ng service stopping.' if [ -f /var/run/syslog-ng.pid ]; then syspid=`/usr/bin/cat /var/run/syslog-ng.pid` [ "$syspid" -gt 0 ] && kill -15 $syspid fi ;; *) echo "Usage: $0 { start | stop }" exit 1 ;; esac ------------------------------------------ Jesse Keefe <jesse.keefe@convergys.com> | Systems Administrator | Convergys Corp. | 229 West Seventh Street | P.O. Box 1638 | Cincinnati, Oh 45201 | (513)723-3689 | -- NOTICE: The information contained in this electronic mail transmission is intended by Convergys Corporation for the use of the named individual or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone (collect), so that the sender's address records can be corrected.
On Tuesday, January 22, jesse.keefe@convergys.com wrote:
For those who asked about starting syslog-ng on boot, here is what I did for Solaris 8. I simply modified the /etc/rc2.d/S74syslog script:
Another alternative that works well for me is adding this to /etc/inittab: sl:234:respawn:/usr/local/sbin/syslog-ng -F -C /logs -u someuser -g somegroup
I would suggest that the scripts be modified to test for proper operations of the daemon as well. If it hangs in startup or somesuch the Admin needs to know about it. This is really true of INITTAB based services I think. Todd ----- Original Message ----- From: "William Yodlowsky" <wyodlows@andromeda.rutgers.edu> To: <syslog-ng@lists.balabit.hu> Sent: Tuesday, January 22, 2002 10:45 AM Subject: Re: [syslog-ng]Syslog-ng on Boot
On Tuesday, January 22, jesse.keefe@convergys.com wrote:
For those who asked about starting syslog-ng on boot, here is what I did for Solaris 8. I simply modified the /etc/rc2.d/S74syslog script:
Another alternative that works well for me is adding this to /etc/inittab:
sl:234:respawn:/usr/local/sbin/syslog-ng -F -C /logs -u someuser -g somegroup
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng
On Tuesday, January 22, todd glassey wrote:
I would suggest that the scripts be modified to test for proper operations of the daemon as well. If it hangs in startup or somesuch the Admin needs to know about it. This is really true of INITTAB based services I think.
True. I threw it out as a concept rather than an implementation recommendation, although my post didn't reflect that... apologies.
----- Original Message ----- From: "William Yodlowsky" <wyodlows@andromeda.rutgers.edu> To: <syslog-ng@lists.balabit.hu> Sent: Tuesday, January 22, 2002 10:45 AM Subject: Re: [syslog-ng]Syslog-ng on Boot
On Tuesday, January 22, jesse.keefe@convergys.com wrote:
For those who asked about starting syslog-ng on boot, here is what I did for Solaris 8. I simply modified the /etc/rc2.d/S74syslog script:
Another alternative that works well for me is adding this to /etc/inittab:
sl:234:respawn:/usr/local/sbin/syslog-ng -F -C /logs -u someuser -g somegroup
-- "There are no mistakes, only happy accidents." -- Bob Ross
Still its important in automating the operations and startup of the system to instrument some form of heart beat. I cant tell you the number of times that a service level heart beat has told me a server is down and the Host's Stack is still up so PING and other ICMP queries all return as alive... very frustrating. Todd ----- Original Message ----- From: "William Yodlowsky" <wyodlows@andromeda.rutgers.edu> To: <syslog-ng@lists.balabit.hu> Sent: Tuesday, January 22, 2002 2:20 PM Subject: Re: [syslog-ng]Syslog-ng on Boot
On Tuesday, January 22, todd glassey wrote:
I would suggest that the scripts be modified to test for proper operations of the daemon as well. If it hangs in startup or somesuch the Admin needs to know about it. This is really true of INITTAB based services I think.
True. I threw it out as a concept rather than an implementation recommendation, although my post didn't reflect that... apologies.
----- Original Message ----- From: "William Yodlowsky" <wyodlows@andromeda.rutgers.edu> To: <syslog-ng@lists.balabit.hu> Sent: Tuesday, January 22, 2002 10:45 AM Subject: Re: [syslog-ng]Syslog-ng on Boot
On Tuesday, January 22, jesse.keefe@convergys.com wrote:
For those who asked about starting syslog-ng on boot, here is what I did for Solaris 8. I simply modified the /etc/rc2.d/S74syslog script:
Another alternative that works well for me is adding this to /etc/inittab:
sl:234:respawn:/usr/local/sbin/syslog-ng -F -C /logs -u someuser -g somegroup
-- "There are no mistakes, only happy accidents." -- Bob Ross
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng
participants (3)
-
jesse.keefeï¼ convergys.com
-
todd glassey
-
William Yodlowsky