However, when following the instructions for "Running Sawmill at System Startup", I get a message that sawmill has started 'OK' and then a subsequent status execution reveals that 'sawmill dead but subsys locked'. Note: If I run the status fast enough after the start command, I see TWO (2) process running, then a subsequent status reveals that it fails.

Some notes on my installation:

o I've copied sawmill6.3.8 to sawmill in /bin

o I've created a sawmilld script in /bin with the commands:

#!/bin/sh
sawmill &

o I've created a script in /etc/rc.d/init.d with the commands:

#!/bin/sh
#
# Startup script for Sawmill

# function library.
. /etc/rc.d/init.d/functions

# See how we were called.
case "$1" in
start)
echo -n "Starting sawmill: "
daemon sawmilld
echo
touch /var/lock/subsys/sawmill
;;
stop)
echo -n "Shutting down sawmill: "
killproc sawmill
echo
rm -f /var/lock/subsys/sawmill
rm -f /var/run/sawmill.pid
;;
status)
status sawmill
;;
restart)
$0 stop
$0 start
;;
reload)
echo -n "Reloading sawmill: "
killproc sawmill -HUP
echo
;;
*)
echo "Usage: $0 {start|stop|restart|reload|status}"
exit 1
esac

exit 0

o I've made the symbolic links (ln -s) in the /etc/rc.d/rcN.d directories as instructed...

o I've made the symbolic link in the /etc/sawmill directory as instructed back to my initial expanded/exploded directory (/root/rpms/sawmill)...

o I've made my sawmilld script in /bin executable with 'chmode a+rx'.

I am trying to start the sawmill server program with the following commands:

/etc/rc.d/init.d/sawmilld start
/etc/rc.d/init.d/sawmilld status {to see if it started properly}

The program seems to try to start and then fail. Is there anything I can do to see what is happening? Please help and advise...

Most Sincerely,
Erik Mlincek
NetPeople, Inc.
http://www.netpeopleinc.com

Install a script to start Sawmill in /etc/rc.d (or /etc/init.d, or however your UNIX variant does it). A sample script, based on the Apache script, is available here <http://www.flowerfire.com/sawmill/sawmill_etc_rcd.sh>. The method varies from UNIX to UNIX, but to give one specific example, in RedHat Linux 7.0 you should call the script sawmilld and put it in /etc/rc.d/init.d, and then make symbolic links to it from the rc0.d - rc6.d directories, encoding into the name of the link whether to Start sawmill at that runlevel, or to Kill it. A good sequence of links is the following:

ln -s /etc/rc.d/init.d/sawmilld /etc/rc.d/rc0.d/K15sawmilld
ln -s /etc/rc.d/init.d/sawmilld /etc/rc.d/rc1.d/K15sawmilld
ln -s /etc/rc.d/init.d/sawmilld /etc/rc.d/rc2.d/K15sawmilld
ln -s /etc/rc.d/init.d/sawmilld /etc/rc.d/rc3.d/S85sawmilld
ln -s /etc/rc.d/init.d/sawmilld /etc/rc.d/rc4.d/S85sawmilld
ln -s /etc/rc.d/init.d/sawmilld /etc/rc.d/rc5.d/S85sawmilld
ln -s /etc/rc.d/init.d/sawmilld /etc/rc.d/rc6.d/K15sawmilld

If you're not sure where to put the Sawmill links or what to call them, and you have Apache installed on your system, look for files shows names contain httpd in /etc/rc.d or /etc/init.d, and use the same names and locations for Sawmill, replacing httpd with sawmilld.

Rename the Sawmill executable to sawmill and put it in /bin or somewhere else in your default path.

Download the script sawmilld <http://www.flowerfire.com/sawmill/sawmilld> and put it in /bin. Make it executable using the command chmod a+rx /bin/sawmilld.

Put a symbolic link to LogAnalysisInfo in /etc/sawmill/LogAnalysisInfo (or you can put the actual directory there), using the ln -s command, e.g. ln -s /usr/home/sawmill/LogAnalysisInfo /etc/sawmill/LogAnalysisInfo (you'll need to create the directory /etc/sawmill first).