lpd: unknown printer in /var/adm/syslog

[M577A2]

I have a customer running SCO 5.0.6a. We recently loaded OSS646B - Execution Environment Supplement (ver 1.1.0j) due to a requirement for running our software. They rebooted the system recently and now /var/adm/syslog is getting the following error 33 times per second:

Jan 29 06:33:20 my_server lpd[Some_PID_Number]: unknown printer: =LP2

The syslog file quickly grew in excess of 175MB. Attempting to run lp to the printer results in the follwing error even though lpd and lpsched are active:

# lp -dLP2 /etc/inittab
request id is LP2-252
lp: connect: Connection refused
jobs queued, but cannot start daemon.

# ps -ef | grep lp
root 220 1 0 08:35:28 ? 00:00:00 /opt/K/SCO/lli/5.0.6a/bin/d
lpid /var/opt/K/SCO/lli/5.0.6a/dlpidPIPE
root 24187 1 82 06:53:26 ? 00:00:02 /usr/lib/lpd
root 26143 1 0 06:53:34 ? 00:00:00 /usr/lib/lpsched

If I stop lpd/lpsched, remove the oss646b, restart lpd/lpsched and then reload the oss646b, then everything works fine until the next reboot. I've actually made entries in /etc/hosts.equiv and /etc/hosts.lpd to no avail.

Has Anybody seen this before? There's nothing on SCO's web site.

 

[PHV]

Can you post the contents of /etc/printcap for the LP2 entry, and the outout produced by the following command ?

ls -al /var/spool/lpd/LP2

Hope This Help
PH.

 

[M577A2]

SCO actually responded and quite quickly! Here is their response:

"Our Support Service engineers have reproduced your reported bug ... This bug has been recently corrected by Engineering a public fix is forthcoming. Currently, workarounds are to remove oss646b(a) or to install a copy of lpd from a 5.0.7 system."

I'll be trying the 5.0.7 lpd solution later today since removal of oss646b is not an option for my customer.

 

[ivessm]

Hey M577A2,

So what have you finally done to put this in check.

I have the same situation on a OS 5.0.5 box.

Looking on SCO site and don't see anything new.

Thanks.

stew

 

[M577A2]

We had SCO 5.0.7 in-house so we used that lpd in place of the one on 5.0.6. SCO has released oss663 to address the problem on SCO 5.0.5

 

[PeterReid]

oss663a also did the biz for me on 5.0.6