by Hi, I am having an terrible time priting since I reinstalled
slackware. I get the following erros when I try and print.
norstar:~$ ls | lpr
norstar:~$
I am not sure why it is trying to "connect:" like htis, it didnt do
this before. I read the lpd manpages and the lpd.perms
file is set up exactly how they say it should be. Is there something
else I should be doing?
----/etc/lpd.perms:
###########################################################################
# LPRng - An Extended Print Spooler System
#
# Copyright 1988-1995 Patrick Powell, San Diego State University
# See LICENSE for conditions of use.
#
###########################################################################
# MODULE: TESTSUPPORT/printer_perms.proto
# PURPOSE: prototype printer permissions file
# $Id: lpd.perms,v 3.1 1997/01/22 23:15:38 papowell Exp $
##########################################################################
# Printer permissions data base
## #
## LPRng - An Enhanced Printer Spooler
## lpd.perms file
##
## Access control to the LPRng facilities is controlled by entries
## in a set of lpd.perms files. The common location for these files
## are: /etc/lpd.perms, /usr/etc/lpd.perms, and /var/spool/lpd/lpd.perms.
## The locations of these files are set by the printer_perms_path entry
## in the lpd.conf file or by compile time defaults in the src/common/defaults.c
## file. In addition to the global permissions files, each spool queue
## can also have a permissions file. This file is searched when information
## or operations on a specific printer is requested.
##
## Each time the lpd server is given a user request or carries out an unspooling
## operation, it searches to the perms files to determine if the action
## is ACCEPT or REJECT. The first ACCEPT or REJECT found terminates the search.
## If none is found, then the last DEFAULT action is used.
##
## Permissions are checked by the use of 'keys' and matches. For each of
## the following LPR activities, the following keys have a value.
##
## Key Match Connect Job Job LPQ LPRM LPC
## Spool Print
## SERVICE S 'X' 'R' 'P' 'Q' 'M' 'C,S'
## USER S - JUSR JUSR JUSR JUSR JUSR
## HOST S RH JH JH JH JH JH
## GROUP S - JUSR JUSR JUSR JUSR JUSR
## IP IP RIP JIP JIP RIP JIP JIP
## PORT N PORT PORT - PORT PORT PORT
## REMOTEUSER S - JUSR JUSR JUSR CUSR CUSR
## REMOTEHOST S RH RH JH RH RH RH
## REMOTEGROUP S - JUSR JUSR JUSR CUSR CUSR
## REMOTEIP IP RIP RIP JIP RIP RIP RIP
## CONTROLLINE S - CL CL CL CL CL
## PRINTER S - PR PR PR PR PR
## FORWARD V - - SA - SA SA
## SAMEHOST V - SA - SA SA SA
## SAMEUSER V - - - SU SU SU
## SERVER V - SV - SV SV SV
##
## KEY:
## JH = HOST host in control file
## RH = REMOTEHOST connecting host name
## JUSR = USER user in control file
## CUSR = REMOTEUSER user from control request
## JIP= IP IP address of host in control file
## RIP= REMOTEIP IP address of requesting host
## PORT= connecting host origination port
## CONTROLLINE= pattern match of control line in control file
## FW= IP of source of request = IP of host in control file
## SA= IP of source of request = IP of host in control file
## SU= user from request = user in control file
## SA= IP of source of request = IP of server host
##
## Match: S = string with wild card, IP = IPaddress[/netmask],
## N = low[-high] number range, V = exact value match.
## SERVICE: 'X' - Connection request; 'R' - lpr request from remote host;
## 'P' - print job in queue; 'Q' - lpq request, 'M' - lprm request;
## 'C' - lpc spool control request; 'S' - lpc spool status request
## NOTE: when printing (P action), the remote and job check values
## (i.e. - RUSR, JUSR) are identical.
##
##
## The special key letter=patterns searches the control file
## line starting with the (upper case) letter, and is usually
## used with printing and spooling checks. For example,
## C=A*,B* would check that the class information (i.e.- line
## in the control file starting with C) had a value starting
## with A or B.
##
## A permission line consists of list of tests and an a result value
## If all of the tests succeed, then a match has been found and the
## permission testing completes with the result value. You use the
## DEFAULT reserved word to set the default ACCEPT/DENY result.
## The NOT keyword will reverse the sense of a test.
##
## Each test can have one or more optional values separated by
## commas. For example USER=john,paul,mark has 3 test values.
## #Do not allow forwarded jobs or requests
## REJECT SERVICE=R,C,M FORWARD
##
# allow root on server to control jobs
ACCEPT SERVICE=C SERVER USER=root
REJECT SERVICE=C
#
# allow same user on originating host to remove a job
ACCEPT SERVICE=M SAMEHOST SAMEUSER
# allow root on server to remove a job
ACCEPT SERVICE=M SERVER USER=root
REJECT SERVICE=M
# all other operations allowed
DEFAULT ACCEPT