09-10-2008
e.g. yesterday I didnt use my scripts. result:
elo6: /home/vbe# lpstat -W
Queue Dev Status Job Files User PP % Blks Cp Rnk
-------------------- -------------- --------- ------ ------------------ ---------- ---- --- ----- --- ---
SC-0-1-HP4M @160 READY
SC-0-1-HP4M: JetDirect lpd: no jobs queued on the port Auto
SC-0-2-LJ4000N @160 READY
: (WARNING) 0781-375 Connection to server failed.
rembak: errno = 4: A system call received an interrupt.
SC-0-2-LJ4000N SC-0-2-LJ4000N HOST_DOWN
SC-0-3-LJ1100 @160 READY
: (WARNING) 0781-375 Connection to server failed.
rembak: errno = 4: A system call received an interrupt.
SC-0-3-LJ1100 SC-0-3-LJ1100 HOST_DOWN
SC-1-1-LJ4050 @160 READY
: (WARNING) 0781-375 Connection to server failed.
rembak: errno = 4: A system call received an interrupt.
SC-1-1-LJ4050 SC-1-1-LJ4050 HOST_DOWN
SC-1-2-HP4 @160 READY
SC-1-2-HP4: JetDirect lpd: no jobs queued on the port Raw
SC-2-1-LJ4100 @160 READY
: (WARNING) 0781-375 Connection to server failed.
rembak: errno = 4: A system call received an interrupt.
SC-2-1-LJ4100 SC-2-1-LJ4100 HOST_DOWN
SC-2-2-HP4 @160 READY
SC-2-2-HP4: JetDirect lpd: no jobs queued on the port Raw
SC-3-HP4M @160 READY
: (WARNING) 0781-375 Connection to server failed.
rembak: errno = 4: A system call received an interrupt.
SC-3-HP4M SC-3-HP4M HOST_DOWN
lpvbe @160 READY
lpvbe: JetDirect lpd: no entries
NOW:
elo6: /home/vbe# lpstat -W
Queue Dev Status Job Files User PP % Blks Cp Rnk
-------------------- -------------- --------- ------ ------------------ ---------- ---- --- ----- --- ---
SC-0-1-HP4M @160 READY
SC-0-1-HP4M: JetDirect lpd: no jobs queued on the port Auto
SC-0-2-LJ4000N @160 READY
SC-0-2-LJ4000N: JetDirect lpd: no jobs queued on this port
SC-0-3-LJ1100 @160 READY
SC-0-3-LJ1100: JetDirect lpd: no jobs queued on the port Auto
SC-1-1-LJ4050 @160 READY
SC-1-1-LJ4050: JetDirect lpd: no jobs queued on this port
SC-1-2-HP4 @160 READY
SC-1-2-HP4: JetDirect lpd: no jobs queued on the port Raw
SC-2-1-LJ4100 @160 READY
SC-2-1-LJ4100: JetDirect lpd: no jobs queued on this port
SC-2-2-HP4 @160 READY
SC-2-2-HP4: JetDirect lpd: no jobs queued on the port Raw
SC-3-HP4M @160 READY
SC-3-HP4M: JetDirect lpd: no jobs queued on the port Raw
lpvbe @160 READY
lpvbe: JetDirect lpd: no entries
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When you do a lpstat -t it displays all your printers and tty values.
Where is the file that stores this information in SCO 5.0.5?
Thanks in advance
Stufine (2 Replies)
Discussion started by: stufine
2 Replies
2. UNIX for Advanced & Expert Users
Hi,
I have been using Hp so far and I am a new user to Solaris..
well, in HP Unix, if I type 'lpstat' if gives me the list of printers connected to the network and their status.. but in solaris it only gives the details if there is any job on the queue. I just want to know what is the... (3 Replies)
Discussion started by: sskb
3 Replies
3. SCO
I don't know if anyone still looks at this forum or not, but here goes.
I've got two identical SCO OpenServer 5.0.7 machines, fully patched and updated. On one the non-root user can do lpstat -p and it will display a list of printers and their status, on the other:
$ lpstat -p
UX:lpstat: ERROR:... (3 Replies)
Discussion started by: checkpro
3 Replies
4. Shell Programming and Scripting
Hi there all,
I got a long list of printers installed and a longer list of printers in my hosts file.
In the hosts file I got a even longer list of printers
in the hosts file I got the IP adress of all printers next to the printer name.
How can I get a script working to get the printers... (0 Replies)
Discussion started by: draco
0 Replies
5. Shell Programming and Scripting
Hi Guys,
I am geting this message ".status: (WARNING): 0781-102 Invalid printer name: xerox".i m reading printer name from a text file.i try to print the value reading from file is correct xerox. if run lpstat -pxerox -l it works fine but when i try to read from file it throughs warining.please... (1 Reply)
Discussion started by: sagii
1 Replies
6. Shell Programming and Scripting
Hi,
here is lpstat command with queue name. queue name is not valid but lpstat takes my local queue and shows the following results.is there any way that i can stop it after waring message and dont take local print queue. i would like to print a message that queue is not valid but when lpstat... (4 Replies)
Discussion started by: sagii
4 Replies
7. AIX
Hi,
I tried to migrate a server, I installed AIX on a new server and I want to configure the printer queues. I copied all of files from the old server where the printer queues are working fine. I followed these steps:
1. copy the /etc/qconfig (make a copy of the original before)
2. Copy the... (10 Replies)
Discussion started by: imad77
10 Replies
8. Solaris
Hi
lpstat reports me "Failed to contact service for xxxxxx: not-found"
lpstat -p test -l
printer test unknown state. enabled since Oct 27 12:01 2009. available.
Remote Name: XXXXXX
Remote Server: sunsrv
Failed to contact service for xxxxxx: not-found
can someone help... (1 Reply)
Discussion started by: xtreams
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
can somebody tell me what is the difference between `lpstat -s` and `lpstat -v` command.
thanks. (3 Replies)
Discussion started by: anandgodse
3 Replies
10. UNIX for Dummies Questions & Answers
Hi all,
Newbie to the site here and fairly novice to UNIX\LINUX so please bear with me.:)
My question is; can the lpstat -t command show the size of the print jobs in mb or gb instead of bytes? They would be much easier to view this way.
For more information of what I'm on about; please... (1 Reply)
Discussion started by: Melikins
1 Replies
LEARN ABOUT DEBIAN
cups-lpd
cups-lpd(8) Apple Inc. cups-lpd(8)
NAME
cups-lpd - receive print jobs and report printer status to lpd clients
SYNOPSIS
cups-lpd [ -h hostname[:port] ] [ -n ] [ -o option=value ]
DESCRIPTION
cups-lpd is the CUPS Line Printer Daemon ("LPD") mini-server that supports legacy client systems that use the LPD protocol. cups-lpd does
not act as a standalone network daemon but instead operates using the Internet "super-server" inetd(8) or xinetd(8). If you are using
inetd, add the following line to the inetd.conf file to enable the cups-lpd mini-server:
printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpd
-o document-format=application/octet-stream
Note: If you are using Solaris 10 or higher, you must run the inetdconv(1m) program to register the changes to the inetd.conf file.
If you are using the newer xinetd(8) daemon, create a file named /etc/xinetd.d/cups containing the following lines:
service printer
{
socket_type = stream
protocol = tcp
wait = no
user = lp
group = sys
passenv =
server = /usr/lib/cups/daemon/cups-lpd
server_args = -o document-format=application/octet-stream
}
OPTIONS
-h hostname[:port]
Sets the CUPS server (and port) to use.
-n
Disables reverse address lookups; normally cups-lpd will try to discover the hostname of the client via a reverse DNS lookup.
-o name=value
Inserts options for all print queues. Most often this is used to disable the "l" filter so that remote print jobs are filtered as
needed for printing; the examples in the previous section set the "document-format" option to "application/octet-stream" which forces
autodetection of the print file format.
PERFORMANCE
cups-lpd performs well with small numbers of clients and printers. However, since a new process is created for each connection and since
each process must query the printing system before each job submission, it does not scale to larger configurations. We highly recommend
that large configurations use the native IPP support provided by CUPS instead.
SECURITY
cups-lpd currently does not perform any access control based on the settings in cupsd.conf(5) or in the hosts.allow(5) or hosts.deny(5)
files used by TCP wrappers. Therefore, running cups-lpd on your server will allow any computer on your network (and perhaps the entire
Internet) to print to your server.
While xinetd has built-in access control support, you should use the TCP wrappers package with inetd to limit access to only those comput-
ers that should be able to print through your server.
cups-lpd is not enabled by the standard CUPS distribution. Please consult with your operating system vendor to determine whether it is
enabled on your system.
COMPATIBILITY
cups-lpd does not enforce the restricted source port number specified in RFC 1179, as using restricted ports does not prevent users from
submitting print jobs. While this behavior is different than standard Berkeley LPD implementations, it should not affect normal client
operations.
The output of the status requests follows RFC 2569, Mapping between LPD and IPP Protocols. Since many LPD implementations stray from this
definition, remote status reporting to LPD clients may be unreliable.
SEE ALSO
cups(1), cupsd(8), inetconv(1m), inetd(8), xinetd(8),
http://localhost:631/help
COPYRIGHT
Copyright 2007-2011 by Apple Inc.
4 August 2008 CUPS cups-lpd(8)