UNIX for Dummies Questions & Answers

any ideas as to why the qdaemon would stop about the same time every other day. nothing has changed on our system.

any ideas would be appreciated.

Use the command ps -ef | grep qdaemon to verify that the qdaemon is not active. If the qdaemon is not active, you should see, at the most, a line of output representing the grep itself. It should look something like this:

root 2992 18792 0 12:46:39 pts/2 0:00 grep qdaemon

If the qdaemon is active, which it almost certainly will not be, you will see a variant of the following line:

root 2980 3652 0 12:41:25 - 0:00 /usr/sbin/qdaemon

If the qdaemon is not active, issue the command startsrc -s qdaemon to restart the qdaemon. If the qdaemon died, it should have been restarted automatically by the srcmstr process, but it doesn't always work, so restart it manually. You should see a variant of this message:

0513-059 The qdaemon Subsystem has been started. Subsystem PID is 3000.

Wait one minute or so and re-issue the command ps -ef | grep qdaemon. Is the qdaemon still active or did it just start and then die? If the qdaemon is no longer active, despite the fact that you just restarted it and received a message stating the qdaemon's process id (PID) and that it was active, check for the existence of the file named /var/spool/lpd/stat/pid. You can do this by issuing the command cat /var/spool/lpd/stat/pid. This file contains the PID of an active qdaemon. When the qdaemon is not active, the file is supposed to be removed.

thank you....this does help me on short cuts instead of going through smit.

but any ideas as to why it continues to go down about the same time just about every other day.