Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!psuvax1!gatech!prism!shangri-la.gatech.edu!robert From: robert@shangri-la.gatech.edu (Robert Viduya) Newsgroups: comp.lang.postscript Subject: Re: How do you count the number of pages in a postscript document? Message-ID: <2681@hydra.gatech.EDU> Date: 21 Oct 89 13:32:33 GMT References: <1955@cunixc.cc.columbia.edu> <1517@tukki.jyu.fi> <1361@scaup.cl.cam.ac.uk> <2677@hydra.gatech.EDU> Sender: news@prism.gatech.EDU Reply-To: robert@shangri-la.gatech.edu (Robert Viduya) Organization: Office of Computing Services, Georgia Tech Lines: 24 > As long as you are able to send a "small job" to the printer to change exit- > server, anybody who wants to cheat, can also do this. Or change it > temporarily, so his pages won't be recorded! Well, first off, I don't change exitserver; I change the serverloop. There's a big difference. Secondly, users can't do an exitserver to change the serverloop if they don't know the exitserver password. Thirdly, since it's also my code that's driving the printers on the host side, I can guarantee that it's my modify-serverloop job that gets to the printer first and not anyone elses. Fourthly, a successful exitserver command sends back a message that looks like: %%[ exitserver: permanent state may be changed ]%% which gives us a convenient red flag for catching any misbehaving users who have managed to figure out the exitserver password. robert -- Robert Viduya robert@shangri-la.gatech.edu Office of Computing Services Georgia Institute of Technology (404) 894-6296 Atlanta, Georgia 30332-0275