On Tue, 24 Sep 2002, John Perkins wrote: > On Tue, 24 Sep 2002 10:54:48 +0200 (CEST) > Martin MOKREJŠ <[EMAIL PROTECTED]> wrote: > > > These are non-comment lines from my lpd.perms: > > > > ACCEPT SERVICE=C SERVER REMOTEUSER=root > > ACCEPT SERVICE=C LPC=lpd,status,printcap > > REJECT SERVICE=C > > ACCEPT SERVICE=M SAMEHOST SAMEUSER > > ACCEPT SERVICE=M SERVER REMOTEUSER=root > > REJECT SERVICE=M > > DEFAULT ACCEPT > > I think you need to make a few additions: > > ACCEPT SERVICE=C UNIXSOCKET > ACCEPT SERVICE=M UNIXSOCKET REMOTEUSER=root > > (tweak those as appropriate for what you want to accept/reject).
Unfortunately, it did not help: ACCEPT SERVICE=C SERVER REMOTEUSER=root ACCEPT SERVICE=C LPC=lpd,status,printcap ACCEPT SERVICE=C UNIXSOCKET ACCEPT SERVICE=M UNIXSOCKET REMOTEUSER=root REJECT SERVICE=C ACCEPT SERVICE=M SAMEHOST SAMEUSER ACCEPT SERVICE=M SERVER REMOTEUSER=root REJECT SERVICE=M DEFAULT ACCEPT To be sure that I understand, this will change behaviour of lpd, not lpr, right? But, killing lpd (the old version) and starting the daemon from 3.8.15 and using lpr from 3.8.15 shows that I still cannot print: $ /software/@sys/usr/bin/lpr-lprng3.5.18 /etc/motd Status Information: sending job 'root@pf-i400+329' to [EMAIL PROTECTED] connecting to 'pf-i400.natur.cuni.cz', attempt 1 connected to 'pf-i400.natur.cuni.cz' requesting printer [EMAIL PROTECTED] job 'root@pf-i400+329' transfer to [EMAIL PROTECTED] failed error 'ERROR TRANSFERRING DATA' sending str '^Blp-pf-i400' to [EMAIL PROTECTED] $ BTW: in lpd.perms.sample are NOT those 2 lines you suggested. Actually, I uesed exatly th esample file (HOWTO refers to lpd.perms.template, but I have only lpd.perms.sample). ;) Also I tried in lpd.conf: default [EMAIL PROTECTED] but this does not help either. :( > > > But why should change the default behaviour? The lpr binary works fine, > > with same config file ... (And I did not mention in the original post, > > that lpd itself has problems to print - I administer the box remotely, but > > users say sometimes they can proint, sometimes not. Reverting to old lpd > > also of course solved their problems. Once more - with same config > > files!). > > This is a functionality change in lpd. You should read through the > list archives to figure out why this change was implemented. I think it > has to do with servers handling MANY jobs in batches...there were some > problems opening many TCP sockets in a short period of time for some > setups. Patrick gave a much better summary when he originally wrote the > code. Hmm, but cold be documented somewhere. Something like "hot topics" would be nice. I believe there was a good reason. Definitely not anything in INSTALL or READMe or HOWTO, if I did not miss it. ;) -- Martin Mokrejs <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs MIPS / Institute for Bioinformatics <http://mips.gsf.de> GSF - National Research Center for Environment and Health Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany tel.: +49-89-3187 3683 , fax: +49-89-3187 3585 ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
