|
Hemo (Programmer) |
19 Jul 07 16:50 |
Wondering if anyone has run across this type of situation before and had any suggestions. First, the system information: CODESCO OpenServer 5.0.7 Ent. with MP 5 installed.
# uname -X
System = SCO_SV
Node = sys_v
Release = 3.2v5.0.7
KernelID = 2003-02-18
Machine = i80386
BusType = ISA
Serial = XXXXXXXXX
Users = 105
OEM# = 0
Origin# = 1
NumCPU = 1
# swconfig -P
Set Release Notes
--- ------- -----
OSS656B - OpenServer Licensing Update OSS656B.5 applied
rs507d - UNIX Runtime System Update rs507d.Un applied
OSS656B - Link Kit Patches OSS656B.5 applied
rs507d - SCO Link Kit Update rs507d.li applied
rs507d - Administration Framework Update rs507d.ad applied
rs507d - SCO Software Manager rs507d.So applied
rs507d - Network Configuration Manager Update rs507d.ll applied
rs507d - SCO Mail User Agents Update rs507d.MA applied
OSS673A for 507 OSS673A.5 applied
rs507d - SCO Srom Driver Update rs507d.Sr applied
rs507d - SCO Blc Driver Update rs507d.Bl applied
rs507d - SCO cga Driver Update rs507d.cg applied
rs507d - SCO ega Driver Update rs507d.eg applied
rs507d - SCO fd Driver Update rs507d.fd applied
rs507d - Iiop Patch rs507d.Ii applied
rs507d - SCO mono Driver Update rs507d.mo applied
rs507d - SCO pa Driver Update rs507d.pa applied
OSS667B for 507 OSS667B.5 applied
rs507d - SCO udi Driver Update rs507d.ud applied
OSS667B for 507 OSS667B.5 applied
rs507d - SCO udi usb Driver Update rs507d.ud applied
rs507d - SCO Wd Driver Update rs507d.Wd applied
rs507d - XServer Update rs507d.XS applied
rs507d - Video Configuration Manager Update rs507d.Vi applied
rs507d - Scosession Update rs507d.XC applied
rs507d - Scologin and Pmwm Update rs507d.Ba applied
rs507d - TCP/IP Runtime Update rs507d.tc applied
OSS672A for 507 OSS672A.5 applied
rs507d - SCO NFS Runtime Update rs507d.nf applied
rs507d - Internet Services Administration Tools U rs507d.At applied
rs507d - SCO SendMail Update rs507d.Se applied
# Having a problem with users submitting jobs to the print spooler. These are HP printers (8150 series) on the TCP/IP networking installed as model 'laserjethpnp' using the HP network printer tools. Root is able to print fine. Users are 'hanging' in the print system. Users are able to submit/cancel their own jobs. Spooler takes the job and appears to be printing, but nothing happens at the printer, lpstat will show that the job is 'on printerxyz' and hang there indefinitely. CODEprinter1-1732 paul 1753 Jul 19 15:43 on printer1 Canceling this 'hung' job will allow the next job in the queue to be attempted, otherwise everything destined for this printer backs up. Users get no error messages, jobs are successfully submitted, but then hang at print time. A look in the /usr/spool/lp/temp directory will show the file being owned by the user and restrictive permissions. CODE-rw------- 1 paul lp 0 Jul 19 15:43 1732
-rw-rw---- 1 lp lp 91 Jul 19 15:43 1732-0 Of course, I can only capture the jobs that aren't printing, but what I see on all of them is the permissions only let the owner of the file read/write to it. Wouldn't this mean the the lp system couldn't read it and causing job to 'hang'? Any thoughts? I've exhausted verifying permissions on directories/files, removed and reinstalled printers, etc.. |
|
Talk To Other Members
Read More Threads Like This One