Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!kings!lau
From: lau@desci.wharton.upenn.edu (Yan K. Lau)
Newsgroups: comp.sys.apollo
Subject: Re: lpr/lpd problems (revisited)
Message-ID: <38900@netnews.upenn.edu>
Date: 7 Mar 91 16:36:34 GMT
References: <1991Mar3.135954.39621@eagle.wesleyan.edu> <1991Mar6.213032.39820@eagle.wesleyan.edu>
Sender: news@netnews.upenn.edu
Organization: A Private Heaven
Lines: 54
Nntp-Posting-Host: kings.wharton.upenn.edu
Originator: lau@kings

In article <1991Mar6.213032.39820@eagle.wesleyan.edu> hdtodd@eagle.wesleyan.edu writes:
>In article <1991Mar3.135954.39621@eagle.wesleyan.edu>, hdtodd@eagle.wesleyan.edu writes:
>> 	I have followed the discussion of lpr problems with interest,
>> since I have the infamous "cannot start daemon" problem. 
>		<stuff deleted>
>
>
>	In trying to work through this, I found that the daemon fails to start
>if I use a fully-articulated Internet address, e.g., mumble.wesleyan.edu, as
>
>	I must have done something stupid when I set up the system six months
>ago and set up some other configuration parameter to expect just "mumble" -- 
>but I can't find it.
>
>	Can anyone suggest a solution to this?
>
My experience with lpr no daemon present is as follows.  I don't know if
this situation applies to you or whether to solution will work in your case.
But, you certainly did not do something stupid.  I had the same problem.
I called Apollo about it.  The lpr group stays that the "solution" was to
name my machine "mumble".  I said that I couldn't do that because we're on
a network.  He then said he'll forward my problem to the networks group
since he doesn't deal with that.  The network person calls me, her suggestion
was to name my hard disk volume "mumble.wesleyan.edu" to match my network
name.  Now that is really wierd!  I couldn't see our users getting used to
that.  But I tried it anyway.  Turns out both "solutions" work but I couldn't
see doing either.

Now for my solution:  We were running ns_helper.  Turns out that when I
added fullnames through edns, everyone was happy.  My machine are still
known by their fullnames to the world.  My volume is still the short name.

(Side note: totally unrelated, the only wierd effect is the Originator:
line above, where is that name coming from? Our rn must be set up wrong.)

I hope my experience helps someone else.

Tidbits: We are running lpd on all our disked machines.  I haven't used
the servername so I don't know how that works.  Our diskless machines
aren't running lpd, lpr doesn't work on them.  Our /etc/printcap is set
up with the pc= to pass the print request on to prf.  We used the lpr
command mostly to receive remote printing requests.  I'm still looking
for some way to stop lpr/lpd from chopping lines at 132 col when sending
to prf.  Does anyone have a filter for this?  Our kludge solution now is
to run the file through a wrap program before sending it to the lpr
command.  We mostly send PostScript files through so 132 col limit messes
up printouts.


Yan.
-- 
   )~  Yan K. Lau    lau@kings.wharton.upenn.edu      The Wharton School
 ~/~   Sheenaphile           128.91.11.233       University of Pennsylvania
 /\    God/Goddess/All that is -- the source of love, light and inspiration!