SUMMARY: setting up a client printer.

From: Steven Sakata (
Date: Tue Apr 25 2000 - 12:59:45 CDT

Thank you to all of you who responded. The winning answer came from
David Foster. I was missing the /etc/inetd.conf "printer" entry and I
needed to reboot the server (i.e., system1). Note, a "kill -HUP" on inetd
was not good enough - I had to reboot. I would get the following error
message when I just did the "kill -HUP":

inetd[176]: printer/tcp: bind: Address already in use

Thanks again, Steven.

On Mon, 24 Apr 2000, Steven Sakata wrote:

> I have one system (i.e., "system1") that I set up a local print queue
> (i.e., "lj1") to a network printer using HP's jetadmin utility. I can send
> print jobs to this printer with no problem.
> I have a second system (i.e., "system2") that I wanted to provide access to
> "lj1" via "system1". I ran the command "lpadmin -p lj1 -s system1" and
> it seemed to create the queue. However, when I tried to send a print job, it
> seems to just stay on "system2". When I submit the "lp" command, I get the
> following message in /var/adm/messages:
> lp[1054]: Warning: Received SIGPIPE; continuing
> Does anyone have any ideas as to what the problem might be?
> Thanks, Steven.

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:06 CDT