>Solaris 2.6
>I have started getting complaints from users that old documents are
>being printer from one of our network printers.
>Looking at the /var/print/spool directory I see that there are 100's of
>spool files. The 10th file , date wise, is .printd.lock
>doing a ps -ef also shows a printd process running
>also there are about 20 lpr processes
>I have no idea whats going on. Is it possible that this printd process
>was interfeering with the spool directory ?
Probably not.
Quote:>What does printd do ?
Catches incoming print jobs from the network, stores them in the
/var/spool/print directory, and makes TCP connections to the network
printer or print server and forwards the print jobs.
Quote:>how can I investigate why spool files for this one particular printer
>are filling up the spool directory ?
What does "lpstat -p printername" say about the printer?
Does "lpstat -t" say anything different?
Quote:>any suggestions would be appreciated and yes I am in RTFM mode.........
I would stop the print system with the "lpshut" command, edit the
inetd.conf file to disable the daemon for incoming print jobs
(the line starts with the word "printer"), and kill off any lpsched,
printd, in.lpd, lp, and lpr processes. Delete the files in the
/var/spool/print directory. It's safe to do that now that there
are no processes that could be using them. Then re-start lpsched
("/etc/init.d/lp start"), and re-enable the print daemon in the
inetd.conf file.
See if cleaning out the spool directory like that gets rid of the
problem.
-Greg
--
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
by