Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site uw-beaver Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxj!mhuxt!houxm!vax135!cornell!uw-beaver!laser-lovers From: laser-lovers@uw-beaver Newsgroups: fa.laser-lovers Subject: Re: Accounting rears its ugly head. Message-ID: <1507@uw-beaver> Date: Fri, 23-Aug-85 00:27:03 EDT Article-I.D.: uw-beave.1507 Posted: Fri Aug 23 00:27:03 1985 Date-Received: Sat, 24-Aug-85 18:21:46 EDT Sender: daemon@uw-beaver Organization: U of Washington Computer Science Lines: 22 From: Marshall RoseI think the best solution is to have the imagen tell the host how many page images it processed and how many pages it printed. I am told that when you connect the imagen to a host with a serial line, that you get back some sort of accounting information (I don't know what; we use the ethernet option and are very happy with it, thank you). I think the reason that the imagen does not return this info via the ethernet is that it closes the connection before it's done printing the job (presumably after it's snarfed the imPress EOF or gets a TCP FIN or whatever). Why it does this, I don't know. However it won't accept a new connection from the net until the first one is closed. After accepting a new connection, it blocks until the job header for the first job is printed. After that data is read from the new connection. Perhaps someone who knows something about the TCP/IP implementation for the Imagen can shed some light here? /mtr