I got this email from a Debian user. He's happy now but i thought I
would pass it on, sorry it's not much to go on.
What happened was lpd was chewing up all the CPU load. He then copied a
3.6.12 lpd and everything went fine. I've asked to see if he still has
the corrupted file somewhere.
I get those xterm messages if I more a binary file.
----- Forwarded message from David Stern -----
hi craig,
i just discovered what was going on, although it's still weird a little
bit--i had some corrupt print jobs in the spool i didn't know about. so i
guess that somehow the old lpd at least understood what they were about
and the new lpd didn't recognize them and had kittens. only think i can
make out from the garbage that printed is "xterm". not sure where the
jobs came from since this is such a new install. hmm..
so, prospective bug closed! :p
david
----- End forwarded message -----
--
Craig Small VK2XLZ GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.eye-net.com.au/ <[EMAIL PROTECTED]>
MIEEE <[EMAIL PROTECTED]> Debian developer <[EMAIL PROTECTED]>
-----------------------------------------------------------------------------
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
