Path: utzoo!utgpu!watserv1!watmath!att!bellcore!bellcore-2!rutgers!cs.utexas.edu!samsung!uunet!mcsun!tuvie!mike
From: mike@tuvie (Inst.f.Techn.Informatik)
Newsgroups: comp.sys.apollo
Subject: Re: Need help with lpr
Message-ID: <1694@tuvie>
Date: 21 Jul 90 13:37:15 GMT
References: <613@tron.UUCP> <4ba5d449.20b6d@apollo.HP.COM>
Reply-To: mike@tuvie.UUCP (Inst.f.Techn.Informatik)
Organization: Technical University of Vienna, AUSTRIA
Lines: 25

In article <4ba5d449.20b6d@apollo.HP.COM> pcc@APOLLO.COM writes:
>** SR10.2:
>
>The world has been made easier at SR10.2.  Just link all the /usr/spool/lpd's
>to one node, create /usr/spool/lpd/servername, which contains the name of the
>ONE node running lpd -- ** NO LEADING // ** -- make sure that lpd runs on
>that one node, and you're all set.  Doing this places restrictions on using
>multiple LPD's (how you can have multiple LPD's, if necessary), but I won't
>go into that here  (especially since I stopped supporting lpd about 6 months
>ago).
>
I think this is *NOT* the best solution to this problem - what happens
if the servernode is down - with the standard lpr/lpd solution it is
queued locally, but this way you'll get an error and that's that.
I wish Apollos could run vanilla BSD UNIX without screwing up
UNIX features. I do not want an improved UNIX, I WANT UNIX!

                                bye,
                                        mike
       ____  ____
      /   / / / /   Michael K. Gschwind             mike@vlsivie.at
     /   / / / /    Technical University, Vienna    mike@vlsivie.uucp
     ---/           Voice: (++43).1.58801 8144      e182202@awituw01.bitnet
       /            Fax:   (++43).1.569697
   ___/