Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!natinst!rpp386!woody From: woody@rpp386.cactus.org (Woodrow Baker) Newsgroups: comp.lang.postscript Subject: Re: Adobe PPD files Summary: more on PPD Message-ID: <17405@rpp386.cactus.org> Date: 5 Dec 89 13:56:20 GMT References: <1025@maxim.erbe.se> <17380@rpp386.cactus.org> Organization: River Parishes Programming, Plano, TX Lines: 28 In article , jtkohl@quicksilver.mit.edu (John T Kohl) writes: > 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!) yep, that would be a good approach, but no one does. Not even Adobe. All Indians, no Chiefs..... Cheers Woody