Hello,
Well, I have no idea what I did but it's working again. I ended up
rebooting several times and clearing out temp files and eventually it
just printed! Now I need to read up on the Solaris printer subsystem.
Thanks to those who replied and those who will reply before they get
this!
My original post:
I have written many times regarding SunOS but now I have one machine
that
is running Solaris 5.4 and I'm having a printer problem.
We have been successfully printing to a Xerox 4900 Color Laser Printer.
At one point no print jobs were getting through. I powercycled bothe
the
printer and the S20 that it is connected to and when I run a lpstat -t I
get the following:
lpstat -t
scheduler is running
system default destination: cool_ps
system for cool_ascii: cool (as printer ascii)
system for cool_ps: cool (as printer ps)
system for cool_pcl: cool (as printer pcl)
cool_ascii accepting requests since Mon Apr 1 11:29:23 EST 1996
cool_ps accepting requests since Mon Apr 1 11:32:50 EST 1996
cool_pcl accepting requests since Fri Mar 29 14:57:11 EST 1996
printer cool_ascii faulted. enabled since Mon Apr 1 11:57:23 EST 1996.
available.
no entries
status: idle
printer cool_pcl faulted. enabled since Mon Apr 1 11:57:23 EST 1996.
available.
no entries
status: idle
character set
Is there any easy way to find out how the printer is faulted? At one
point I used
lpc (God only knows how) and tryed to down the printer and run a clean
and I got a message telling me that the printer was busy. I removed the
print jobs from /var/spool/lp/requests and /tmp.
I am only somewhat familiar with the SunOS printer subsystem and know
much less about the SOLARIS system. HELP!
------------------------------------------------------------------------
Thanks to :
From:
sagray@amp.com (Steve Gray)
To:
sysadmin@astrosun.tn.cornell.edu
> We have been successfully printing to a Xerox 4900 Color Laser Printer.
> At one point no print jobs were getting through. I powercycled bothe the
> printer and the S20 that it is connected to and when I run a lpstat -t I
> get the following:
Hi, Vic. I've had this problem when the printer has a paper
jam, runs out of paper, or does something else to cause the
lp system to fault.
To get it going again, I just stopped the lp system with
/usr/lib/lpshut, then restarted the lp system with /usr/lib/lpsched.
To eliminate the faulting, use the lpadmin command like this:
/usr/sbin/lpadmin -p <printer> -F continue
By default, the lp system waits for the administrator to correct
faults and restart the printing system. The above command causes
the printing system to restart on its own once the fault is fixed.
Another problem I've seen, and only in Solaris 2.4 (which you're
running), is the occasional failure of the lp system. I've had to
run /usr/lib/lpsched in a cron at 10-minute intervals. It's not a
pretty fix, but it works...
______
/ __/ /____ _ _____ Steve Gray (sagray@amp.com)
_\ \/ __/ -_) |/ / -_) AMP Incorporated, Hbg PA
/___/\__/\__/|___/\__/ (717) 671-7133
------------------------------------------------------------------------
From:
Asim Zuberi <asim@psisa.com>
To:
Systems Administrator <sysadmin@astrosun.tn.cornell.edu>
If you still have problems with your printing call me. We will try to
configure the printer bsd way.
--
***************************************************************
Systems Administrator
---------------------
Space Sciences Building CRSR
Mail all system related problems to one of the following:
sysadmin@astrosun.tn.cornell.edu root@astrosun.tn.cornell.edu
sysadmin@spacenet.tn.cornell.edu root@spacenet.tn.cornell.edu
or see
Vic Germani in room 402 germani@astrosun.tn.cornell.edu
***************************************************************
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:56 CDT