Re: IP address printing w/ LPRng
Jim:
Could you repost that message you sent yesterday? My windows machine went crazy last
night and said I had 4,000+ messages this morning (mostly duplicates). I then went a
little crazier, and just started deleting left and right, and somehow accidentally deleted
your last message. Thanks,
Brian
Brian Morgan wrote:
> I've redone my printcap file to read:
> lp1|12.10.35.3|Remote printer entry:\
> :lp=:\
> :rm=12.10.35.3:\
> :rp=text:\
> :sd=/var/spool/lpd/12.10.35.3:\
> :mx#0:\
> :sf:\
> :sh:
> Shouldn't that lp line read lp=/dev/lp1:\ ???
> I also modified my hosts.lpd file to include 12.10.35.3
> I also created the 12.10.35.3 spool directory in /var/spool/lpd (anything I need to do
> with that?)
> I still have 2 lpd print spooling services starting up when I boot my machine.
> Shouldn't that be changed?
> After all the changes, I've tried printing using
> cat [filename] > /dev/lp1
> and nothing happens.
>
> Lewis, James M. wrote:
>
> > Brian,
> >
> > Those things have 2 printer names configured. They are "text" and
> > "raw". The text one adds cr when it sees an lf and the raw one does
> > not. I don't know if there is a way to make new printer names for
> > those things. You might telnet into it to see if you can.
> >
> > Umm, I just checked one and you don't seem to be able to change the
> > printer names...
> >
> > Second to last line needs a ":\". You might also try using a null
> > entry for the device. My printcap looks like this:
> >
> > lp1|rm164_hp|Remote printer entry:\
> > :lp=:\
> > :rm=rm164_hp:\
> > :rp=raw:\
> > :sd=/var/spool/lpd/rm164_hp:\
> > :mx#0:\
> > :sf:\
> > :sh:
> >
> > You have to make sure the spool directory exists. You also have to
> > have an entry in the hosts file or dns for the name in the "rm=" entry.
> > You can also use an ip-addr. Depending on your situation, one usually
> > works better than the other. For places that have a bunch of printers, the
> > dns entry makes life easier. You can swap out hardware and change
> > the dns entry without having to change a bunch of servers hosts files
> > (or printcap files). Doing it with dns is a pain if you only have one
> > or two servers/workstations (like a home network)...
> >
> > I'm using lpr, not lprng, but they should work the same.
> >
> > jim
> >
> > ----------
> > From: Brian Morgan[SMTP:bmorgan@greenville.edu]
> > Sent: Tuesday, July 07, 1998 9:59 AM
> > To: Debian User group
> > Cc: The recipient's address is unknown.
> > Subject: IP address printing w/ LPRng
> >
> > I posted some questions about printing to an ip address earlier. Thanks
> > for those who have helped so far.
> >
> > More questions:
> >
> > I'm running hamm, 2.0.33 and LPRng print spooling package. I'm trying
> > to print to
> > an HP laserjet through a jetdirect card with an ip address.
> >
> > I've edited my /etc/printcap file to look like this:
> > rlp|Remote printer entry:\
> > :lp=/dev/lp1:\
> > :rm=12.10.35.3:\
> > :rp=debian test printer:\
> > :sd=/var/spool/lpd/lp1:\
> > :mx#0
> > :sh:
> >
> > Does that look right so far? Are the :\ marks correct? They weren't in
> > the file origianally, but I added them from a Unix machine's example.
> >
> > Also, on startup, it appears that there are 2 lpd print spoolers started
> > since I installed the LPRng package. This doesn't seem right. What can
> > I do about it?
> >
> > In /var/spool/lpd directory, I have the following directories and files:
> >
> > lp lp1 lpd.lock.debian.printer
> > Shouldn't there be an rlp directory? I created the lp1 directory. Is
> > that right?
> > In the lp directory, the status.lp file contains many "/dev/lp1 cannot
> > connect" errors
> >
> > I've modified the /etc/hosts.lpd file to include 2 computers that I want
> > to be able to connect to the printcap file. Is there a way to set this
> > so all computer can connect, and not just a limited few?
> >
> > >From what I've indicated here, is there anything else I need to do to be
> > able to print? Any permissions I need to check out, esp. in the spool
> > directory? Make your answers as simple as possible, because I'm still
> > fairly new at this.
> >
> > Thanks for your help,
> >
> > Brian
> >
> > --
> > Brian Morgan bmorgan@greenville.edu
> > Computer Service Specialist bmorgan@debian.greenville.edu
> > Greenville College http://www.gvc.net/~jedi
> >
> > ========================
> > "Surely you can't be serious!"
> > "I am serious, and don't call me Shirley!"
> >
> > --
> > Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org <
> > /dev/null
> >
> > --
> > Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
> --
> Brian Morgan bmorgan@greenville.edu
> Computer Service Specialist bmorgan@debian.greenville.edu
> Greenville College http://www.gvc.net/~jedi
>
> ========================
> "Surely you can't be serious!"
> "I am serious, and don't call me Shirley!"
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
--
Brian Morgan bmorgan@greenville.edu
Computer Service Specialist bmorgan@debian.greenville.edu
Greenville College http://www.gvc.net/~jedi
========================
"Surely you can't be serious!"
"I am serious, and don't call me Shirley!"
--
Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
Reply to: