no it's like hosts.equil
just put a hostname to a line in it
(or a ip address)
eg
#START OF FILE
machine1
machine2
machine3
203.35.152.123
#END OF FILE
On Fri, 31 Dec 1999, Darrell Burkey wrote:
> > hosts.lpd is the file which controls lpd remote permissions same as the
> > rhosts etc...
>
> Yes, I've done that. I assume it is the same format as hosts.allow/deny? But
> even so, doesn't it seem a bit odd that the syslog would contain an error
> from lpd that:
>
> > > Dec 30 14:25:19 opus lpd[22620]: unknown printer /dev/lp0
> > > Dec 30 14:29:35 opus lpd[22633]: unknown printer /dev/lp0
>
> When that same device is being used without problem by the host machine?
>
>
> > On Thu, 30 Dec 1999, Darrell Burkey wrote:
> >
> > > After hours of reading every faq and scouring every newsgroup and web
> site I
> > > could think of I can't find help on what I would assume if a fairly easy
> > > question.
> > >
> > > I have two Redhat 6.0 installations here that are networked together. I
> > > simply want to print from one to the other that has a printer on it.
> When I
> > > print from the client machine the job just sits in the local print
> queue.
> > > lpq shows the status of the job and has the message "waiting for queue
> to be
> > > enabled on opus". lpq on opus shows the queue enabled so I'm a bit
> confused.
> > >
> > > Here's the printcap of the client machine:
> > >
> > > lp:\
> > > :sd=/var/spool/lpd/lp:\
> > > :mx#0:\
> > > :sh:\
> > > :rm=opus:\
> > > :rp=lp:\
> > > :if=/var/spool/lpd/lp/filter:
> > >
> > > and I have the client machine listed in hosts.allow on the server. I
> even
> > > got desperate and created a hosts.lpd and hosts.equiv file with the
> client
> > > machine listed.
> > >
> > > Then I started lpd up with logging to watch what happens when the client
> > > machine attempts to send a print job. An error is generated by lpd,
> > > "unknown printer /dev/lp0" which seems odd as the printcap file on the
> > > server (on which printing works fine) uses this definition:
> > >
> > > lp:\
> > > :sd=/var/spool/lpd/lp:\
> > > :mx#0:\
> > > :sh:\
> > > :lp=/dev/lp0:\
> > > :if=/var/spool/lpd/lp/filter:
> > >
> > > How can /dev/lp0 work on the server but generate an error from lpd when
> > > started from a remote client?
> > >
> > > Here's some output from the system log generated when I printed from the
> > > remote client machine and then from the server with the printer
> attached:
> > >
> > > Dec 30 14:25:19 opus lpd[22620]: unknown printer /dev/lp0
> > > Dec 30 14:29:35 opus lpd[22633]: unknown printer /dev/lp0
> > > Dec 30 14:30:06 opus kernel: parport0: PC-style at 0x278 [SPP,PS2]
> > > Dec 30 14:30:06 opus kernel: parport0: no IEEE-1284 device present.
> > > Dec 30 14:30:06 opus kernel: lp0: using parport0 (polling).
> > >
> > > Confused as usual, help appreciated.
> > >
> > > Cheers and happy holidays.
> > >
> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > Darrell Burkey
> > > http://www.tucan.net/darrell
> > > 0408 622 647
> > >
> > > --
> > > SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
> > > To unsubscribe send email to [EMAIL PROTECTED] with
> > > unsubscribe in the text
> > >
>
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
