Hello,
I have researched this and found many comments concerning the print issue with SCO UNIX OS 5.0.5 but thought I would add something interesting.
Customer system is SCO OS 5.0.5 with following patches:
rs505a & OSS636A as well as others.
-rws--x--x 1 root bin 70364 Apr 17 2003 lpd@
Whenever the system is rebooted the syslog file fills up with the "unknown printer ???" error and the ??? are the last 3 letters of the first line of the /etc/printcap file.
The one solution I have found is to call /etc/printcap up in vi and add something to the first line, save it, which causes the printcap file to be re-read. The errors stop logging to the syslog file and all is fine.
I generally have a couple of days to do this because nothing crashes until the / hard disk becomes completely full.
The system's /etc/printcap file is:
# Remote Line Printer (BSD format) this
lp05:\
:lp=:rm=mainoff-hplj4100:sd=/usr/spool/lpd/lp05:
lp07:\
:lp=:rm=ps0:sd=/usr/spool/lpd/lp07:
lp08:\
:lp=:rm=bldg5-epsondfx:sd=/usr/spool/lpd/lp08:
lp10:\
:lp=:rm=bldg6-zebra02:sd=/usr/spool/lpd/lp10:
lp11:\
:lp=:rm=bldg1-hplj4100:sd=/usr/spool/lpd/lp11:
lp15:\
:lp=:rm=bldg12-kyocera1650:sd=/usr/spool/lpd/lp15:sh:
lp16:\
:lp=:rm=bldg2-printek:sd=/usr/spool/lpd/lp16:sh:
lp9:\
:lp=:rm=bldg12-epsondfx:sd=/usr/spool/lpd/lp9:sh:
lp25:\
:lp=:rm=bldg1-epsondfx:sd=/usr/spool/lpd/lp25:sh:
lp19:\
:lp=:rm=bldg1-kyocera2050:sd=/usr/spool/lpd/lp19:sh:
I would suspect one solution is to go find a newer SCO OS version, copy the /usr/lib/lpd program from it and place it on the SCO OS 5.0.5 machine. Does anyone think that might work or do you have any other suggestions?
Thanks.
stew
I have researched this and found many comments concerning the print issue with SCO UNIX OS 5.0.5 but thought I would add something interesting.
Customer system is SCO OS 5.0.5 with following patches:
rs505a & OSS636A as well as others.
-rws--x--x 1 root bin 70364 Apr 17 2003 lpd@
Whenever the system is rebooted the syslog file fills up with the "unknown printer ???" error and the ??? are the last 3 letters of the first line of the /etc/printcap file.
The one solution I have found is to call /etc/printcap up in vi and add something to the first line, save it, which causes the printcap file to be re-read. The errors stop logging to the syslog file and all is fine.
I generally have a couple of days to do this because nothing crashes until the / hard disk becomes completely full.
The system's /etc/printcap file is:
# Remote Line Printer (BSD format) this
lp05:\
:lp=:rm=mainoff-hplj4100:sd=/usr/spool/lpd/lp05:
lp07:\
:lp=:rm=ps0:sd=/usr/spool/lpd/lp07:
lp08:\
:lp=:rm=bldg5-epsondfx:sd=/usr/spool/lpd/lp08:
lp10:\
:lp=:rm=bldg6-zebra02:sd=/usr/spool/lpd/lp10:
lp11:\
:lp=:rm=bldg1-hplj4100:sd=/usr/spool/lpd/lp11:
lp15:\
:lp=:rm=bldg12-kyocera1650:sd=/usr/spool/lpd/lp15:sh:
lp16:\
:lp=:rm=bldg2-printek:sd=/usr/spool/lpd/lp16:sh:
lp9:\
:lp=:rm=bldg12-epsondfx:sd=/usr/spool/lpd/lp9:sh:
lp25:\
:lp=:rm=bldg1-epsondfx:sd=/usr/spool/lpd/lp25:sh:
lp19:\
:lp=:rm=bldg1-kyocera2050:sd=/usr/spool/lpd/lp19:sh:
I would suspect one solution is to go find a newer SCO OS version, copy the /usr/lib/lpd program from it and place it on the SCO OS 5.0.5 machine. Does anyone think that might work or do you have any other suggestions?
Thanks.
stew