Date: Fri, 3 Nov 2000 03:20:03 -0800 (PST) From: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/7973: lpd: Bad control file owner in case of remote printing Message-ID: <200011031120.DAA76013@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/7973; it has been noted by GNATS. From: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz> To: Garance A Drosihn <drosih@rpi.edu> Cc: freebsd-gnats-submit@FreeBSD.org, andreas@FreeBSD.org Subject: Re: bin/7973: lpd: Bad control file owner in case of remote printing Date: Fri, 3 Nov 2000 12:10:32 +0100 This PR bin/7973 was originated 2 years ago and I have somewhat different point of view on this problem now, so: Garance A Drosihn wrote (2000/11/02): > I understand the issue you are talking about, but I would argue > that print filters have no business reading the control files. > The control files are "a protocol" of sorts for an lpr process > (or some other lpd process) to communicate with an lpd process. Yes, I agree. > Imagine what happens if we want to change the format of cf > files, which we may very well want to do (if we accept jobs > from via protocols other than lpd). I don't think print > filters should have any idea of the format of cf files. I think we do not want to change the format of control files because there is RFC 1179: Line Printer Daemon Protocol. However, if we want to accept jobs from other protocols, control files can have another format and you are right that the problem would be back. > So, my question to you is, What is the exact information that > your print filters need from the cf-files? For your print The motivation for my patch was because of apsfilter-5.x.x. It reads control files and acquires host name, user name a job name. On-coming apsfilter-6.x.x gets all this information from command line parameters, where current lpr implementation offers user name (-n) and host name (-h) only. Job name is missing. The main author of apsfilter is Andreas Klemm (andreas@FreeBSD.ORG), so maybe we may talk with him too (... CCed to him). > filters, would it be better if they picked up that information > (whatever you need) via some environment variables that lpd > might set before starting up your filter? Environment variables or command line parameters. We have -n and -h already there, so the only missing parameter is job name (LPRng has -f). If we look at LPRng further, it has another very interesting parameter: -Z z_opts, where z_opts are random parameters from user passed directly to print filters. > This is the solution I would prefer to implement. Me too. How much of free time do you have (and possibly others, if any) for work on FreBSD's lpr subsystem? Thanks. -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011031120.DAA76013>