Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!rice!sun-spots-request
From: wargaski@acns.nwu.edu (Robert E. Wargaski Jr.)
Newsgroups: comp.sys.sun
Subject: Re:  printcap for a large site; how???
Keywords: Miscellaneous
Message-ID: <5128@brazos.Rice.edu>
Date: 19 Feb 90 08:43:43 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 19
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n50
X-Sun-Spots-Digest: Volume 9, Issue 50, message 6

In X-Sun-Spots-Digest: Volume 9, Issue 50, message 2, Fred Comins writes:
>We have many printers and are getting another 45 laser jets.  The problem
>is that all users want to be able to get to any of the printers.   I'm
>looking for advice on the easiest way to keep this managed.  Currently we
>were planning to use rdist with 1 master printcap with an entrie for every
>printer.  Any better ideas??  Do I have to have a spool directory for
>each??  thanks

I have read the introductory document for the Palladium Printing System
from MIT's Project Athena; it sounds like they have the best approach to
managing a large printing environment.

I wish I could offer more practical advice, but we have not yet built the
programs it requires (e.g. Kerberos, Zephyr, Hesiod, if recall serves me
correctly).  At least it is an alternative you can check out.

Robert E. Wargaski Jr.			| This is stupid. -- Vila
wargaski@acns.nwu.edu			| When did that ever stop us. -- Avon
NU Distributed Systems Support		| . . . #include <disclaimer.h> . . .