From: jmorriso@rflab.ee.ubc.ca (John Paul Morrison) Subject: Re: Printing on a Remote SPARCPrinter (kernel 0.99pl9) Date: 14 May 1993 07:27:56 GMT
In article <1su83pINNq8g@senator-bedfellow.MIT.EDU> bpburke@athena.mit.edu (Brian P Burke) writes:
>This is the entry from my printcap file:
>
>lp|duchess|duchess, SPARCprinter:\
> lp=:rm=duchess:rp=duchess:mx#0:sd=/var/spool/duchess:\
> lf=/var/spool/duchess/log:
>
>as root I get the following results
># lpr .emacs
>lpr: connect: No such file or directory
>jobs queued, but cannot start daemon.
># lpq
>Warning: no daemon present
>Rank Owner Job Files Total Size
>1st root 13 .emacs 8848 bytes
>#
>
>as a normal user I get:
>/ lpr .emacs
>lpr: Who are you?
>/
is there a printer named duchess running on a machine nameed duchess?
because that's what you are specifying. I've never played with
a SparcPrinter before; I assume it runs right off the netwrork
as a host and a printer.
It's very difficult to debug without seeing the printcap running on
the remote machine.
Make sure you arent having any hostname problems by putting
duchess in /etc/hosts.
>
>Is my printcap correct? Do I need to have a file /dev/printer? What permissions
>should lpr,lpq,lprm, the spool file/directories have? (I've tried those listed
>in the README/FAQ without success)
>
I won't go into all the permissions and all that; the subject's
been beaten to death.
>
>Possible contributing factor:
>The Sun's are using NIS should that be a problem?
>
this is your best bet. running as root on your local machine is fine
for debugging a local printer, but the remote host will almost
certainly tell you to screw off when it sees root trying to
do things from another machine.
there are several ways to authorize access to remote printers.
for example, we use netgroups, and authorized print clients
are members of a netgroup. In /etc/hosts.lpd you would have
a line like :+@clients or something like that.
we need to know more about your setup. There are printcap options
to authorize only if the client has a userid on the print server.
Instead of netgroups, you could have individual host entries
which authorize your machine to print.
you should make sure you'r in a DNS with a proper name for your
machine so that other machines (like the remote printer) will see
a name and not just an IP address. (the permission is based on names
not addresses).
If your're confident that your local printing is set up properly,
then make a userid on your machine that will correspond to a normal
id on the other network machines. try lpr from that ID, and not root,
because the remote host may not accept root.
In any case, just look at the other machines on the
network, and use the same file permissions, copy what you need
to from their printcap etc.
>
>Thanks for your help.
>-Brian
>
>
>--
>----------
>brianb@atc.ll.mit.edu
>bpburke@athena.mit.edu
-- ______________________________________________________________________________ John Paul Morrison | University of British Columbia, Canada | Hey hey!! Ho ho!! Electrical Engineering | Tax & spend liberals jmorriso@ee.ubc.ca VE7JPM | have got to go!! ________________________________________|____________________________________