Date: Fri, 15 Jun 2001 23:00:01 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Marvin McNett <mmcnett@cs.ucsd.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: lpd problem Message-ID: <p05100e01b7507b0ed112@[128.113.24.47]> In-Reply-To: <3B207665.798C2CD3@cs.ucsd.edu> References: <3B17BA5D.953634EA@cs.ucsd.edu> <p05100e1ab7408627fecd@[128.113.24.47]> <3B207665.798C2CD3@cs.ucsd.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:53 PM -0700 6/7/01, Marvin McNett wrote: >Garance, > >Thanks for the reply. I'm still having this strange problem. >I've noticed that I need to restart lpd every time I log in >(not just a boot time as I originally stated). This makes no >sense to me. Well, I was hoping someone else would answer, because it doesn't make a whole lot of sense to me either... :-) You mention that you have to restart lpd every time you log in. I assume that means the lpd process is still running fine (and has to be stopped), it's just that the stupid queue for the Lexmark isn't working. About the only thing I can guess is something in your environment space. Change the print-filter that lexmark provided so it will log the current environment somewhere when the filter starts up (if it's a binary program, then wrap the program with a script). Just a simple 'date >> /tmp/stupidQ; set >> /tmp/stupidQ;' should do the trick. Then try various experiments to see what is different between the times when the queue works, and when it doesn't. Sorry I can't be more help. While I do a lot with printing, it's almost all experience with network-printers. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05100e01b7507b0ed112>