On Mon, 17 Dec 2001, Patrick Powell wrote: > > If you're looking for something to do Patrick :) there have been > > murmurings about why printer daemons NEED port 515 open when a Unix > > socket could do the trick as well. Obviously if the local printer > > is used by remote clients it is needed and this change would mean > > a non-standard extension but it shouldn't be that hard I suspect. > Originally this was the way that it was done. You ALWAYS ran a > server on your local machine, and then you would connect to a UNIX > socket. The server was the one that did the network stuff. And > then people decided that they wanted lightweight spooling - i.e. > - no server on the localhost.
perhaps I'm too dense but could you point me to some readings that specify exactly what the client and server pieces do. I havent read rfc1179 - and was hoping to avoid that. But I'm still not clear on which tasks the client does -- -- David Bear College of Public Programs/ASU 480-965-8257 ...the way is like water, going where nobody wants it to go ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
