9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Conor Williams" <connorwilliamsie@aol.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] lpdaemon probs (fix)
Date: Thu, 27 Feb 2003 09:59:34 +0000	[thread overview]
Message-ID: <032301c2de46$ee289830$9949800a@will551> (raw)
In-Reply-To: <2fe448800f0bb9f4affd7924ad2648b2@collyer.net>

hey Geoff
thanks for youre interest...
got it running last night - spent half the night hacking the
lpdaemon.c code (/root/sys/src/cmd/lp) and traced the problem
to the fork and exec - which didnt seem to be running - so ran
touch and that worked then watched the processes being spawned on
the server and found that lp was being spawned...
so eventually after trying differnt things traced the problem to the
namespace... what happened was the parallel port wasnt bound for
user none coming into the box...
so  a bind -a '#'L2 /dev in the /rc/bin/service/tcp515 file before the
lpdaemon line fixed it... jumping around the room last night!! This
fixed the "read error: connection lost line" aswell! So I can now print from
my diskless terminal to my server which has the printer hanging out
of its parallel port.
Q. Has no-one come across that before?
The devices file I had created was actually ok (it is quite similar to
the one I posted)
l8r
will551

----- Original Message -----
From: "Geoff Collyer" <geoff@collyer.net>
To: <9fans@cse.psu.edu>
Sent: Tuesday, February 25, 2003 11:50 PM
Subject: Re: [9fans] lpdaemon probs


> I think we need your /sys/lib/lp/devices file (or at least the entries
> relevant to your printers), not an approximation, to debug this.
> There should be a dozen fields in most entries; they should look
> something like this (all one line):
>
> fn          2C-501  olive.cs.bell-labs.com  tcp!fn.cs.bell-labs.com!9100
81920  post+600dpi+duplex+hp4simx  generic generic generic generic
tcppost FIFO
>
> Also, could you run this and send us the output:
>
> flag x +
> echo fs $fs fileserver $fileserver
> 9fs other
> ls -ld /lp /n/other/lp
>
>



  reply	other threads:[~2003-02-27  9:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 19:04 [9fans] A proposal regarding # in bind rog
2003-02-24 19:04 ` rob pike, esq.
2003-02-24 19:53   ` Jack Johnson
2003-02-25  4:37   ` Martin C.Atkins
2003-02-25 11:02     ` chris
2003-02-25 14:01       ` Martin C.Atkins
2003-02-25 14:11         ` Russ Cox
2003-02-25 14:17           ` Martin C.Atkins
2003-02-25 14:34             ` Russ Cox
2003-02-25 14:36               ` Russ Cox
2003-02-25 14:52                 ` Ronald G. Minnich
2003-02-25 19:57                   ` northern snowfall
2003-02-25 16:49                 ` Dan Cross
2003-02-26  5:12                   ` Martin C.Atkins
2003-02-24 19:29 ` Fco.J.Ballesteros
2003-02-24 22:34 ` George Michaelson
2003-02-24 23:32   ` Bruce Ellis
2003-02-25  5:02     ` Martin C.Atkins
2003-02-25 11:19       ` chris
2003-02-25 14:06         ` Martin C.Atkins
2003-02-26  0:04         ` Bruce Ellis
2003-02-26  6:06           ` Skip Tavakkolian
2003-02-25  5:00 ` Martin C.Atkins
2003-02-25  9:05   ` [9fans] lpdaemon probs Conor Williams
2003-02-25 10:07     ` Geoff Collyer
2003-02-25 10:33       ` Conor Williams
2003-02-25 23:50         ` Geoff Collyer
2003-02-27  9:59           ` Conor Williams [this message]
2003-02-27 20:57             ` [9fans] lpdaemon probs (fix) Geoff Collyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='032301c2de46$ee289830$9949800a@will551' \
    --to=connorwilliamsie@aol.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).