Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!cs.utexas.edu!samsung!think!mintaka!snorkelwacker!bloom-beacon!bloom-beacon.mit.edu!jtkohl From: jtkohl@quicksilver.mit.edu (John T Kohl) Newsgroups: comp.lang.postscript Subject: Re: Adobe PPD files Message-ID: Date: 4 Dec 89 18:42:09 GMT References: <1025@maxim.erbe.se> <17380@rpp386.cactus.org> <1989Dec3.024451.11099@utzoo.uucp> <17399@rpp386.cactus.org> Sender: root@athena.mit.edu (Wizard A. Root) Reply-To: jtkohl@ATHENA.MIT.EDU Organization: MIT Project Athena Lines: 19 In-Reply-To: woody@rpp386.cactus.org's message of 4 Dec 89 12:59:48 GMT In article <17399@rpp386.cactus.org> woody@rpp386.cactus.org (Woodrow Baker) writes: >... but there are many legitimate >reasons to exit the server. Most apps do it, and because they do it, changing >the server password is tantamount (spelling?) to throwing the app out. sure, >you can go in and change the preamble. It might work. I think a better solution is to lobby the application developers to add an option to their programs that allow a user to specify the exitserver password. This allows the shared environments to be carefully controlled, while allowing people to get useful stuff printed (assuming they either know the password or know how to find the SysOp who does). If the application developers don't put this feature in their application, then find some competitor who does! -- John Kohl or Digital Equipment Corporation/Project Athena (The above opinions are MINE. Don't put my words in somebody else's mouth!)