Hi John,

I assume you are running a samba share printer with windows clients sending print jobs to the linux box. Since the printer goes down every 31 days, it sound like some print job is executing either from a window scheduler or the linux corntab file once ever 31 days. The output must be directed to the default printer "lp" or "lp1" and evidentially the printer or the print daemon can't handle it. Here is a list of print command you can enter on the linux box command line or look up using the man (manual help):

lp status
lpc
lpq
lprm

Probably what you will need to do is a "lp status" to get the status of the printer. Then you could do a lpq command to get the jobid number that the printer is stuck on. Then use the lprm command to kill that print job using its jobid. Then use the "lpc restart all" command to restart lpd. It seem like there should be a good GUI to handle these command by now, but I do not have a printer currently coming off my linux box and cannot tell you for sure. I use a printer hung off a window NT server to handle all my network printing including sending linux print jobs to it. Sorry I'm not more up on the linux lpd right now.

You will want to track down the print job that is causing the hang and remove it from corntab, schduler, or maybe some custom perl or other deamon.

Try using the "ps -a" to see if you can spot same strange process running on the linux box. Also, it is possible that apache, postgres, etc send status report to the printer once every 31 days, etc. Your best bet is to query the printer once it stop working (eg lpq) to see what the printer daemon can tell you.