Re: Print queues on Solaris 8

From: ML Starkey (martha.starkey_at_sun.com)
Date: 04/13/04


Date: Tue, 13 Apr 2004 12:55:21 -0400

James Goodwill wrote:
> Hi,
>
> I've set up a number of print queues on my Sun Solaris 8 server. The
> printers are managed by NT print servers, running Microsoft TCP/IP printing
> (lpd).
>
> The queues were set up with the following command:
>
> lpadmin -p <printer_name> -s <NT print server>!<printer_name>
>
> This solution works just fine for printing. The problem I have is when the
> NT print server is unavailable, due to network or physical failure.
>
> I would expect prints, issued from the UNIX server with the lp command,
> would remain in the UNIX print queue, and their status monitored with the
> lpstat -p <printer_name> command.
>
> However I don't see any prints queued up, after issuing the lpstat command.
>
> Any suggestions as to why this my be?
>
> Regards,
> JG
>
>

Because the -o option is better for monitoring requests. lpstat -p just
  gives status of the printer queue, but not any requests. Maybe that
seems odd to you but that's just the way it is.

lpstat -t gives output requests that are waiting on the machine from
which you issue the command, but it appears at the very bottom, as the
-t option gives you just about every detail about the printers you have
on the system.



Relevant Pages

  • Re: !!HELP!! Pulling my hair on this one. Printer problems. Really need some help on this.
    ... If the server tried to contact a printer and could not, say because of a sporadic hardware issue, it might report the printeras offline. ... I think that what I would do next would be to delete all the printers, then go into Server Properties and delete all the drivers. ... So I think for now if I can resolve the issue as to why I cannot remove and delete the print queues from my SBS server then I can try to reinstall from scratch without the existing print queues still in place. ... By centralizing the spooler you can control access, do "grouped" deployments, such as department/building/remote printer locations using group policy, upgrade a driver on the server and have all workstations get the new driver automatically, and...ultimately...usually a better troubleshooting experience when problems arise because you know the driver, the port, and don't have several workstations with different configurations floating out there. ...
    (microsoft.public.windows.server.sbs)
  • LPR command now causes continuous 60% cpu usage?
    ... We're migrating to server 2003. ... We have put print queues on one of our Server 2003 machines and installed ... For example, this command runs fine: ... It does not matter if the lpr command is issued remotely or from a command ...
    (microsoft.public.windows.server.migration)
  • LPR command now causes continuous 60% cpu usage?
    ... We're migrating to server 2003. ... We have put print queues on one of our Server 2003 machines and installed ... For example, this command runs fine: ... It does not matter if the lpr command is issued remotely or from a command ...
    (microsoft.public.win2000.printing)
  • Re: !!HELP!! Pulling my hair on this one. Printer problems. Really need some help on this.
    ... If you have another server, and if you can share and use the printers from there, can't you just leave them there until you are able to add more drive space to the SBS? ... It can't be my hub because other wall jacks that have workstations connected are plugged into the same. ... So I think for now if I can resolve the issue as to why I cannot remove and delete the print queues from my SBS server then I can try to reinstall from scratch without the existing print queues still in place. ...
    (microsoft.public.windows.server.sbs)
  • Re: Print Server Advertizement Problems
    ... Each building has a domain controller. ... Building B and C have a single server that is ... the printers in the main headquarters. ... The only difference is that the print queues ...
    (microsoft.public.windows.server.general)

Quantcast