01-20-2009
Upon each bootup /dev/lp0 is getting created with permissions to allow root and group lp rw access.
The printer shows unavailable. print jobs error out saying "unable to write to /dev/lp0"
cupsd is running as root
parallel is running as lp
As soon as I add +rw to all users it is fine. This does not feel like the correct "solution".
10 More Discussions You Might Find Interesting
1. Linux
Hello,
I am using version:
cups-config --version - 1.2.4
However, when i use the -o land or -o landscape command it doesn't print in Landscape.
I have the same problem on another server. (Both running CENTOS).
Does landscape printing work in CUPS? Is there a fix?
Thanks in an... (0 Replies)
Discussion started by: stuaz
0 Replies
2. UNIX for Dummies Questions & Answers
Hello.
I have a slackware system running cups with an HP laserJet 2100 connected via parallel port in ECP mode. Print jobs are working. Very slowly.
15K test print out of cups takes about 2 minutes to complete.
When the printout is on the way to the printer, the process "parallel" uses... (0 Replies)
Discussion started by: agentrnge
0 Replies
3. SCO
Hi, i'm running Openserver 5.0.7 as a CUPS client for a Linux server. The root user can issue a "lpstat -t" to see the printers and can submit jobs without issues.
The problem presents when I try to work as a regular user. If I issue an "lpstat -t" all I get after a few seconds is "lpstat:... (1 Reply)
Discussion started by: cyruspy
1 Replies
4. Debian
I am trying to print from Debian and receive the following message: "Unable to open device file"/dev/lp0": Permission Denied"
The permissions for lp0 are 666.
Advice and comments, please.
:wall:
Thanks (0 Replies)
Discussion started by: woofy613
0 Replies
5. AIX
Hello all.
I am setting up a queue under AIX 4.2.1 to print to a remote Linux CUPS queue. At present I can print to the queue remotely from Windows but not AIX. What I am seeing is lpstat reads the state of the remote queue but at job submission time I am getting backend exit fatal errors. The... (4 Replies)
Discussion started by: tgx
4 Replies
6. UNIX for Advanced & Expert Users
I ported application from SysV to Linux and run into troubles with printing.
Application uses lp and HP JetDirect-based printers, it inserts HP control codes in the file and uses plain lp -d dest doc-file command to print it.
The Linux (Ubuntu 8) has CUPS system, which I am not familiar... (0 Replies)
Discussion started by: migurus
0 Replies
7. UNIX for Advanced & Expert Users
Hi Guys,
I've inherited a mess of an infrastructure in my new job, there hasn't been a sys admin in post for about a year, so things are falling apart. The first thing to break after I started was the printer server. I have it working again, and people can print, however it's very slow, slower... (0 Replies)
Discussion started by: rudigarude
0 Replies
8. Red Hat
Hi All,
Having searched for a solution to this issue i found no suggestions which help my particular problem.
I am getting the following error message on 1 of the 3 printers i have configured:
recoverable: Network host 'xxx.xxx.xxx.xxx' is busy; will retry in 30 seconds
All 3 printers are... (0 Replies)
Discussion started by: Tommyk
0 Replies
9. UNIX for Advanced & Expert Users
Hello Experts,
I have been facing an issue with printing through cups configured on Linux server.
All was going on well but all of a sudden the printers started giving an error message, "Unsupported format application/postscript!" and we cant get any prints of any printer.
Need your help as... (2 Replies)
Discussion started by: Rockyc3400
2 Replies
10. Shell Programming and Scripting
Objective: To recreate the partitioning setup of /dev/sda on /dev/sdc
How would I parse the below information and initialize variables
(an array?) that can be used to build sgdisk commands in a script, regardless of the number of partitions?
Something along the lines of:
sgdisk -n... (12 Replies)
Discussion started by: RogerBaran
12 Replies
LEARN ABOUT OSF1
port_names
ports(7) Miscellaneous Information Manual ports(7)
NAME
ports, port_names - Device (tty and lp) names for serial and parallel ports
SYNOPSIS
Default Serial Ports:
/dev/tty00
/dev/tty01 (not present on a single-port system)
Parallel Port:
/dev/lp0
DESCRIPTION
AlphaStation and AlphaServer systems provide one or two 9-pin serial communication ports. These ports are usually labelled 1 (COMM1) and 2
(COMM2), but they may be identified by different icons. Using the appropriate serial cable and terminator, you can connect a serial
printer, external modem, or character-cell terminal to a serial port. Most AlphaStation and AlphaServer systems also provide one parallel
port, for use with a parallel printer.
When you add a device to your system, the installation documentation may instruct you to map the device pathname to the port. These
devices are located in the /dev directory.
For serial-line ports, the two default device pathnames are: This pathname always maps to 1, COMM1, the lowest port number, an icon for a
terminal console, or the only serial port (on a single-port system). This pathname always maps to 2, COMM2, the next numbered port, or (if
one serial port is labeled with an icon for a terminal console) the remaining serial port.
If your system hardware has been extended to include additional serial ports, the pathnames /dev/tty02, /dev/tty03, and so forth, may also
be available to you. However, most systems have only /dev/tty00 and /dev/tty01 as the device pathnames for serial ports.
The one parallel port on an AlphaStation or AlphaServer may be labeled with the word printer or a printer icon. On some systems, the paral-
lel port may not be labeled. The device pathname for the parallel port is /dev/lp0. Currently, Tru64 UNIX does not fully support parallel
printers, so fewer devices are connected to this port as compared to serial ports.
If you are connecting a terminal console to your system, it must be connected to the serial port mapped to /dev/tty00. For other serial
devices, it does not matter which of the serial ports you choose for the connection. For example, suppose you are setting up a system that
has two serial ports, labeled 1 and 2. You intend to use a serial-line terminal rather than a workstation monitor as the system console and
also want to connect a serial-line printer to the system. In this case, you must connect the terminal to the port labeled 1 (with the
device pathname /dev/tty00). Therefore, you must connect the printer to the remaining port labeled 2 (with the device pathname /dev/tty01).
If, for the same type of system, you intend to use a workstation monitor as the system console, it does not matter which serial port you
use for a serial-line printer or modem. In other words, you can connect the printer to either port 1 (with pathname /dev/tty00) or port 2
(with pathname /dev/tty01). When prompted to enter a /dev/tty** pathname by the lprsetup script or the Print configuration tool in the CDE
Application Manager, you would specify /dev/tty00 if you connected the printer to port 1 or /dev/tty01 if you connected the printer to port
2.
See the System Administration manual for more information on setting up consoles (including remote consoles) and printers. See the
modem(7) reference page for more information on setting up modems.
SEE ALSO
Commands: lprsetup(8)
Devices: ace(7), modem(7)
System Administration delim off
ports(7)