Re: lprm says Permission denied (fwd)
On Fri, 21 Mar 1997, John Goerzen wrote: But that still doesn't solve the problem of viewing the Unix print queue from within Windows. That works with regular lpr, but not lprng. i had no problems with the print queue when i used it on my system. this was with win95, not win3 if that makes any difference. Unfortunately, i can't check it again right now because i got sick of win95 crashing all the time and reformatted the disk as a linux only machineat some time in the future i'll add another drive and make it dual boot win95/linux. sorry that this isn't any help to you, but all i can say is that i don't recall that i had to do anything special to get it working. i added fairly obvious stuff to the smb.conf file (which i included in my last message on this topic) and just connected to the printer on the win95 box through the network neighbourhood browser. In all, except for some initial problems i had with PCL printing, it took about half an hour to get up and running including RTFM. have you tried hunting through the samba web site? there is a lot of good information about samba in there, as well as FAQs and archives of mailing lists. i don't recall the URL but it is easy to find from Yahoo etc. also, lprng probably has a web site too - there may be good info there. try an altavista search for 'samba near lprng' and other suitable search phrases. craig
Re: lprm says Permission denied (fwd)
But that still doesn't solve the problem of viewing the Unix print queue from within Windows. That works with regular lpr, but not lprng. On Mar 5, Craig Sanders wrote: but that's not necessary at all. with samba, printers listed in /etc/printcap appear on the Win3/Win95/etc machines printer list (this is the default for the debian package - you can turn it off if you like) - Win users can select it and print to it just like any other printer. Here's an excerpt of relevant parts from my /etc/smb.conf file which works on my network. [global] printing = lprng load printers = yes [printers] comment = All Printers browseable = no path = /tmp printable = yes public = no writable = no create mode = 0700 Once you've set this up, you should be able to see the linux box's printer(s) in Network Neighbourhood on the Win95 machines. Can't remember what the Win3 equivalent is, but the linux printers show up on Win3 too. I have samba, lprng, and magic-filter installed. it works brilliantly. craig FFrom [EMAIL PROTECTED] Tue Mar 4 18:11:53 1997 Return-Path: jgoerzen Received: from mail.midusa.net ([EMAIL PROTECTED] [127.0.0.1]) by complete.org (8.8.5/8.8.4) with SMTP id SAA10400 for jgoerzen; Tue, 4 Mar 1997 18:11:52 -0600 Received: from master.debian.org by services.midusa.net via SMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for [EMAIL PROTECTED] id RAA03490; Tue, 4 Mar 1997 17:22:41 -0600 Received: (qmail 10545 invoked by uid 888); 4 Mar 1997 23:34:44 - Delivered-To: [EMAIL PROTECTED] Received: (qmail 10542 invoked by uid 888); 4 Mar 1997 23:34:44 - Delivered-To: debian-devel@lists.debian.org Received: (qmail 10540 invoked from network); 4 Mar 1997 23:34:42 - Received: from hur-s0.fuller.edu (HELO waterf.org) ([EMAIL PROTECTED]) by master.debian.org with SMTP; 4 Mar 1997 23:34:42 - Received: from localhost [127.0.0.1] (debian) by waterf.org with smtp (Exim 1.60 #1) id 0w23ax-0001tY-00 (Debian); Tue, 4 Mar 1997 15:25:47 -0800 Date: Tue, 4 Mar 1997 15:25:46 -0800 (PST) From: Christoph [EMAIL PROTECTED] To: Nils Rennebarth [EMAIL PROTECTED] cc: Debian Development debian-devel@lists.debian.org Subject: Re: Hylafax In-Reply-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by complete.org id SAA10400 There is a hylafax package in experimental packaged by me needing work. Look through the archive of debian-devel. Someone else wanted to take it on. On Tue, 4 Mar 1997, Nils Rennebarth wrote: There had been several people mentioning they'd make a package from it. Who finally took it now? Reason: I do need a central faxserver here, and might contribute some work do testing... Nils -- \ /| Nils Rennebarth --* WINDOWS 42 *-- | Schillerstr. 61 / \| 37083 Göttingen | ++49-551-71626 Micro$oft's final answer | http://www.nus.de/~nils --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- Please always CC me when replying to posts on mailing lists. rom [EMAIL PROTECTED] Tue Mar 4 18:11:54 1997 Return-Path: jgoerzen Received: from mail.midusa.net ([EMAIL PROTECTED] [127.0.0.1]) by complete.org (8.8.5/8.8.4) with SMTP id SAA10403 for jgoerzen; Tue, 4 Mar 1997 18:11:54 -0600 Received: from master.debian.org by services.midusa.net via SMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for jgoerzen id RAA02059; Tue, 4 Mar 1997 17:17:11 -0600 Date: Tue, 4 Mar 1997 17:17:11 -0600 From: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] |
Re: lprm says Permission denied (fwd)
Nils == Nils Rennebarth [EMAIL PROTECTED] writes: Nils On Tue, 4 Mar 1997, Craig Sanders wrote: On Mon, 3 Mar 1997, Nils Rennebarth wrote: lprng has removed the possibility to automatically remove Files after printing. This is however necessary to remove spooled jobs. How do you work around this problem? I'm not sure what you mean. Files in the lprng spool directories do get automatically deleted after printing...so you must be talking about something else. Nils I must confess that it was long ago I tried to set up printing Nils from Windows clients with samba. It worked by copying the Nils to-be-printed files to /tmp on unix and issuing a lpr Nils command. I then was puzzled about the many big files in /tmp Nils with strange names until I got the idea to add a -r switch to Nils the lpr command to remove files after printing. It worked from Nils then on and I never tried to setup anything and only remembered Nils that the -r switch was vital for operation with samba. The latest lprng ignores this switch and the -s (symlink) switch, but accepts them now. Too many people were having problems with stupid programs (including the Oracle database) that made bad requests (and couldn't be set to do anything else) to the printer subsystem. -r isn't used because lprng is completely network based. (i.e. even on a local machine the file will not just be copied from a location on disk). This is a security feature. -s is similar. Ahh another note. One fo LPRng's `features' is a much heightened security over the basic lpr. More informative output from lpq requests. Easier running modification of the daemon. Better support for filters. (I switched a bunch of machines over from different printing systems lp, lpr based. The users were a little thrown off by the different output format, but it made dealing with the printers from machine to machine much easier). Jim -- @James LewisMoss | [EMAIL PROTECTED] | Blessed Be! @http://www.cs.sc.edu/~moss | [EMAIL PROTECTED] | Linux is cool! @Argue for your limitations and sure enough, they're yours. Bach
Re: lprm says Permission denied (fwd)
On Mon, 3 Mar 1997, Nils Rennebarth wrote: On Sun, 2 Mar 1997, Craig Sanders wrote: actually, it's completely untrue. samba works very well with lprng. lprng has removed the possibility to automatically remove Files after printing. This is however necessary to remove spooled jobs. How do you work around this problem? I'm not sure what you mean. Files in the lprng spool directories do get automatically deleted after printing...so you must be talking about something else. If you're talking about creating, printing, and then deleting temporary files then a wrapper script can be used. craig
Re: lprm says Permission denied (fwd)
On Tue, 4 Mar 1997, Craig Sanders wrote: On Mon, 3 Mar 1997, Nils Rennebarth wrote: lprng has removed the possibility to automatically remove Files after printing. This is however necessary to remove spooled jobs. How do you work around this problem? I'm not sure what you mean. Files in the lprng spool directories do get automatically deleted after printing...so you must be talking about something else. I must confess that it was long ago I tried to set up printing from Windows clients with samba. It worked by copying the to-be-printed files to /tmp on unix and issuing a lpr command. I then was puzzled about the many big files in /tmp with strange names until I got the idea to add a -r switch to the lpr command to remove files after printing. It worked from then on and I never tried to setup anything and only remembered that the -r switch was vital for operation with samba. Nils -- \ /| Nils Rennebarth --* WINDOWS 42 *-- | Schillerstr. 61 / \| 37083 Göttingen | ++49-551-71626 Micro$oft's final answer | http://www.nus.de/~nils
Re: lprm says Permission denied (fwd)
On Sun, 2 Mar 1997, Hamish Moffatt wrote: On Mar 03, 1997 at 08:58:41PM +1100, Craig Sanders wrote: well, actually i had a few initial hassles getting the win95 box to print with the PCL driver. Postscript worked fine (through ghostscript to my HP4L), but PCL failed. Eventually somebody on debian-user suggested that I put check_for_nonprintable no in /etc/lpd.conf - as Strange, because I don't have that in smb.conf, and I print PCL to my new HP5L from Win95 boxes just fine. The 'check_for_nonprintable' is in lpd.conf, NOT smb.conf. I vaguely recall that this was such a FAQ that it was made the default setting (dont take my word for it though) Craig
Re: lprm says Permission denied (fwd)
John == John Goerzen [EMAIL PROTECTED] writes: John Goerzen writes: This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. Why won't samba not work with it? Please file an appropriate bug against the samba package. John Because Samba depends on the output formats of the lp* John commands, in particular, lpq. It parses the output and John converts it to the format suitable for displaying to Windows John users. John Since LPRNG's lpq is different that LPR's lpq output, samba John cannot parse it correctly. -- John Goerzen | Running Debian John GNU/Linux (www.debian.org) Custom Programming | John [EMAIL PROTECTED] | A suggestion for people using Lprng and having problems is to check out the Lprng mailing list (10-20 messages a day - see the doc dir. for info). I joined a few weeks ago and they have covered this problem (Samba) and many others; and Patrick Powell (the author) is extremely helpful in fixing problems and adding new features - this is perhaps yet another good reason to switch to Lprng (how much new development is occurring with lpr ?), Adrian
Re: lprm says Permission denied (fwd)
I had tried the first item you suggested before reverting back to normal lpr, I do recall. I also seem to remember that in some of Samba's documentation, the lprng option was mentioned, while in other areas where the options for printing were listed, lprng was not mentioned. I do not recall if I tried the second thing, but lpq, lprm, and lpr all worked fine from the local box, and lpr worked from Win95. If somebody could print, I would think that they would also have permission to view the queue. On Mar 3, Craig Sanders wrote: On Sun, 2 Mar 1997, John Goerzen wrote: i've got it running on my system, using lprng magicfilter with . samba no problems. it works. Not in my experience. I also tried lprng, magicfilter, and samba. I found the same nonprintable option and turned it off. The Win95 box appeared to print correctly, BUT it could NOT view the print queue, delete sent jobs, etc. With lpr instead of lprng, the Win95 box could do all of that like it is supposed to be able to. a couple of things that might help: 1. check your /etc/smb.conf. Does it have a line like: printing = lprng in the [global] section see man pages for samba and smb.conf - samba has specific support for lprng. 2. check your /etc/lpd.perms - you may not have set up the permissions correctly to allow the win95 box to see the queue and/or delete jobs. craig -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] |
Re: lprm says Permission denied (fwd)
On Sun, 2 Mar 1997, Craig Sanders wrote: actually, it's completely untrue. samba works very well with lprng. lprng has removed the possibility to automatically remove Files after printing. This is however necessary to remove spooled jobs. How do you work around this problem? Nils -- \ /| Nils Rennebarth --* WINDOWS 42 *-- | Schillerstr. 61 / \| 37083 Göttingen | ++49-551-71626 Micro$oft's final answer | http://www.nus.de/~nils
Re: lprm says Permission denied (fwd)
William Chow [EMAIL PROTECTED] writes: On Sat, 1 Mar 1997, John Goerzen wrote: This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. Doesn't getting rid of name canonizing in lpr work? Just get the source of an older version of lpr or unpatch the current sources or get an older lpr binary and it should work. Does this break lpr over network? I prefer to have canonizing in lpr work correctly instead of removing canonizing. Perhaps someone just needs to get the lpr source code and do debugging on it... True ... Sven -- Sven Rudolph [EMAIL PROTECTED] ; WWW : http://www.sax.de/~sr1/
Re: lprm says Permission denied (fwd)
Scott Stanley [EMAIL PROTECTED] writes: Can anyone tell me what the differences are between lpr and lprng. In what ways has lprng been ``enhanced and extended'', to quote the package description. Read /usr/doc/lprng/Intro.txt.gz and others. Sven -- Sven Rudolph [EMAIL PROTECTED] ; WWW : http://www.sax.de/~sr1/
Re: lprm says Permission denied (fwd)
Craig Sanders [EMAIL PROTECTED] writes: On Sun, 2 Mar 1997, Hamish Moffatt wrote: On Mar 03, 1997 at 08:58:41PM +1100, Craig Sanders wrote: well, actually i had a few initial hassles getting the win95 box to print with the PCL driver. Postscript worked fine (through ghostscript to my HP4L), but PCL failed. Eventually somebody on debian-user suggested that I put check_for_nonprintable no in /etc/lpd.conf - as Strange, because I don't have that in smb.conf, and I print PCL to my new HP5L from Win95 boxes just fine. The 'check_for_nonprintable' is in lpd.conf, NOT smb.conf. I vaguely recall that this was such a FAQ that it was made the default setting (dont take my word for it though) Currrently it is only default in the version that is in experimental (because it has some other bugs). It will be default in the next Debian release. Sven -- Sven Rudolph [EMAIL PROTECTED] ; WWW : http://www.sax.de/~sr1/
Re: lprm says Permission denied (fwd)
Adrian Phillips [EMAIL PROTECTED] writes: A suggestion for people using Lprng and having problems is to check out the Lprng mailing list (10-20 messages a day - see the doc dir. for info). I joined a few weeks ago and they have covered this problem (Samba) and many others; and Patrick Powell (the author) is extremely helpful in fixing problems and adding new features - this is perhaps yet another good reason to switch to Lprng (how much new development is occurring with lpr ?), That's the reason why a) using LPRng and b) maintaining a Debian package for LPRng is much easier for me compared to lpr. BTW: There are maintained versions of lpr, but there are that many (the *BSDs, and probably some Linux versions). Unfortunately the *BSD versions don't compile on Linux, and I don't know which Linux-ported lpr versions are well-maintained. Sven -- Sven Rudolph [EMAIL PROTECTED] ; WWW : http://www.sax.de/~sr1/
Re: lprm says Permission denied (fwd)
On Mon, 3 Mar 1997, John Goerzen wrote: I had tried the first item you suggested before reverting back to normal lpr, I do recall. I also seem to remember that in some of Samba's documentation, the lprng option was mentioned, while in other areas where the options for printing were listed, lprng was not mentioned. I do not recall if I tried the second thing, but lpq, lprm, and lpr all worked fine from the local box, and lpr worked from Win95. If somebody could print, I would think that they would also have permission to view the queue. I have switched back to regular lpr myself. I tried lprng briefly, but the errors I was getting didn't make any sense to me at all, so I just switched back to regular lpr. I still haven't fixed my lpr problem, but I think I am getting closer. Basically, what is happening is that when I print a file, the printer starts up but all that comes out is a blank page. I know there is still a line feed problem (as there is initially with many printers), but the file I am printing has text on the first line that should show fine. I have worked through the printing HowTo, but I haven't managed to figure this one out. When I print a file, it is getting sent to the spool directory just fine, but somewhere between there and the printer, all the data is being lost.. Scott On Mar 3, Craig Sanders wrote: On Sun, 2 Mar 1997, John Goerzen wrote: i've got it running on my system, using lprng magicfilter with . samba no problems. it works. Not in my experience. I also tried lprng, magicfilter, and samba. I found the same nonprintable option and turned it off. The Win95 box appeared to print correctly, BUT it could NOT view the print queue, delete sent jobs, etc. With lpr instead of lprng, the Win95 box could do all of that like it is supposed to be able to. a couple of things that might help: 1. check your /etc/smb.conf. Does it have a line like: printing = lprng in the [global] section see man pages for samba and smb.conf - samba has specific support for lprng. 2. check your /etc/lpd.perms - you may not have set up the permissions correctly to allow the win95 box to see the queue and/or delete jobs. craig -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] |
Re: lprm says Permission denied (fwd)
John Goerzen writes: This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. Why won't samba not work with it? Please file an appropriate bug against the samba package. Because Samba depends on the output formats of the lp* commands, in particular, lpq. It parses the output and converts it to the format suitable for displaying to Windows users. Since LPRNG's lpq is different that LPR's lpq output, samba cannot parse it correctly. -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] |
Re: lprm says Permission denied (fwd)
On Sat, 1 Mar 1997, Scott Stanley wrote: On Sat, 1 Mar 1997, John Goerzen wrote: This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. This is nice to know actually, it's completely untrue. samba works very well with lprng. i've got it running on my system, using lprng magicfilter with samba. no problems. it works. well, actually i had a few initial hassles getting the win95 box to print with the PCL driver. Postscript worked fine (through ghostscript to my HP4L), but PCL failed. Eventually somebody on debian-user suggested that I put check_for_nonprintable no in /etc/lpd.conf - as soon as I did this, i could print PCL. The problem wasn't in lprng, or in samba, it was in my config. If I had RTFM it wouldnt have been a problem at all. Sounds like the thing to do is work on lpr to get it working. Besides, I am running into as many problems getting lprng to work as I was lpr. But, I think the lpr problems might be easier to track down i disagree. lpr seems to be quite badly documented (i.e. almost none). lprng has good documentation. Can anyone tell me what the differences are between lpr and lprng. In what ways has lprng been ``enhanced and extended'', to quote the package description. it seems to be a bit more flexible in what you can do with filters and network printers. e.g. i've got an HP4L connected to my main workstation siva (a 486-100 with 32mb). Mostly what i print is postscript stuff which means i have to use ghostscript. This works well, except that siva is so overworked at the moment that i really notice the system slowing down when i print. I used lprng to send postscript printjobs to kali (my newish 32mb cyrix 686-100). kali processes the print job with gs, and then dumps the PCL output back to siva for printing. Setting this up was quite easy. I could have moved the printer to kali's parallel port but that would have meant crawling under tables etc to move the cable. I don't like crawling under tables...in fact, I loathe it. lprng also seems much more configurable for permissions etc. craig
Re: lprm says Permission denied (fwd)
On Mar 03, 1997 at 08:58:41PM +1100, Craig Sanders wrote: well, actually i had a few initial hassles getting the win95 box to print with the PCL driver. Postscript worked fine (through ghostscript to my HP4L), but PCL failed. Eventually somebody on debian-user suggested that I put check_for_nonprintable no in /etc/lpd.conf - as Strange, because I don't have that in smb.conf, and I print PCL to my new HP5L from Win95 boxes just fine. Hamish -- Hamish Moffatt, [EMAIL PROTECTED], Melbourne, Australia. Student, computer science computer systems engineering. 3rd year, RMIT. http://yallara.cs.rmit.edu.au/~moffatt CPOM: [ ] 40% PGP key available from web page above.
Re: lprm says Permission denied (fwd)
On Mar 2, Craig Sanders wrote: On Sat, 1 Mar 1997, Scott Stanley wrote: On Sat, 1 Mar 1997, John Goerzen wrote: This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. This is nice to know actually, it's completely untrue. samba works very well with lprng. i've got it running on my system, using lprng magicfilter with samba. no problems. it works. Not in my experience. I also tried lprng, magicfilter, and samba. I found the same nonprintable option and turned it off. The Win95 box appeared to print correctly, BUT it could NOT view the print queue, delete sent jobs, etc. With lpr instead of lprng, the Win95 box could do all of that like it is supposed to be able to. -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] |
Re: lprm says Permission denied (fwd)
On Sun, 2 Mar 1997, John Goerzen wrote: i've got it running on my system, using lprng magicfilter with . samba no problems. it works. Not in my experience. I also tried lprng, magicfilter, and samba. I found the same nonprintable option and turned it off. The Win95 box appeared to print correctly, BUT it could NOT view the print queue, delete sent jobs, etc. With lpr instead of lprng, the Win95 box could do all of that like it is supposed to be able to. a couple of things that might help: 1. check your /etc/smb.conf. Does it have a line like: printing = lprng in the [global] section see man pages for samba and smb.conf - samba has specific support for lprng. 2. check your /etc/lpd.perms - you may not have set up the permissions correctly to allow the win95 box to see the queue and/or delete jobs. craig
Re: lprm says Permission denied (fwd)
This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. On Wed, 26 Feb 1997 [EMAIL PROTECTED] wrote: Much Deleted. The real fix seems to go to lprng. That's the official position of the maintainer as well, as stated in a msg. to this list last year. I'll do it as soon as I have a chance. If the recommended fix (by the package maintainer even) is to switch from lpr to lprng, shouldn't lpr be switched out of Standard and lprng moved from Optional into Standard? I just happen to be having some problems setting up lpr as well. I think I'll switch to lprng before spending any more time. Scott Carlos -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] |
Re: lprm says Permission denied (fwd)
On Sat, 1 Mar 1997, John Goerzen wrote: This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. Doesn't getting rid of name canonizing in lpr work? Just get the source of an older version of lpr or unpatch the current sources or get an older lpr binary and it should work. Does this break lpr over network? Perhaps someone just needs to get the lpr source code and do debugging on it... Will
Re: lprm says Permission denied (fwd)
On Sat, 1 Mar 1997, John Goerzen wrote: This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. This is nice to know Sounds like the thing to do is work on lpr to get it working. Besides, I am running into as many problems getting lprng to work as I was lpr. But, I think the lpr problems might be easier to track down Can anyone tell me what the differences are between lpr and lprng. In what ways has lprng been ``enhanced and extended'', to quote the package description. Scott On Wed, 26 Feb 1997 [EMAIL PROTECTED] wrote: Much Deleted. The real fix seems to go to lprng. That's the official position of the maintainer as well, as stated in a msg. to this list last year. I'll do it as soon as I have a chance. If the recommended fix (by the package maintainer even) is to switch from lpr to lprng, shouldn't lpr be switched out of Standard and lprng moved from Optional into Standard? I just happen to be having some problems setting up lpr as well. I think I'll switch to lprng before spending any more time. Scott Carlos -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] -- John Goerzen | Running Debian GNU/Linux (www.debian.org) Custom Programming| [EMAIL PROTECTED] |
Re: lprm says Permission denied (fwd)
John Goerzen writes: This is *not* an acceptable fix. Other packages, for isntance Samba, will **NOT** work with lprng. Why won't samba not work with it? Please file an appropriate bug against the samba package. Regards Joey -- / Martin Schulze * Debian Linux Maintainer * [EMAIL PROTECTED]/ / http://www.debian.org/ http://home.pages.de/~joey/
Re: lprm says Permission denied (fwd)
Scott Stanley [EMAIL PROTECTED] writes: The real fix seems to go to lprng. That's the official position of the maintainer as well, as stated in a msg. to this list last year. I'll do it as soon as I have a chance. If the recommended fix (by the package maintainer even) is to switch from lpr to lprng, shouldn't lpr be switched out of Standard and lprng moved from Optional into Standard? I tried to push LPRng as the default, but I learned that there is still software (e.g. netatalk) that relies on subtle properties of classic BSD lpr, so dropping lpr is no option yet. Sven -- Sven Rudolph [EMAIL PROTECTED] ; WWW : http://www.sax.de/~sr1/
Re: lprm says Permission denied (fwd)
[EMAIL PROTECTED] writes: Yes. The suggestion is wrong, the suggestion is just a hack. The problem is due to an incoherence between lprm/lpr/lpd. I sent a patch for this last year, I think it was applied but it may have been dropped. I haven't followed lpr*.deb since, because for me it's working and I don't want to touch it ever again. I think I applied something that should correct this, but obviously it doesn't work. If you could afford the time please check your patch against the current lpr and try to find the difference. Otherwise simply send me your patch. Besides this mess, lpr has security problems as well. The latest buffer overrun is fixed, so I'm not aware of an existing problem. The real fix seems to go to lprng. That's the official position of the maintainer as well, as stated in a msg. to this list last year. I'll do it as soon as I have a chance. True, but I had to learn that LPRng doesn't work in some environments, so we have to keep lpr. Sven -- Sven Rudolph [EMAIL PROTECTED] ; WWW : http://www.sax.de/~sr1/
Re: lprm says Permission denied (fwd)
Hi! something must be wrong with my lpd-setup. When a user starts a print job, s/he can't cancel it anymore. Example: (user 'spiegl') $ lpr abc.txt $ lpq lp is ready and printing Rank Owner Job Files Total Size active spiegl 27 abc.txt 47978 bytes $ lprm 27 cfA027Aa00860: Permission denied cfA027Aa00860: Permission denied $ ls -laF total 54 drwxrwsr-x 2 root lp 1024 Feb 24 01:39 ./ drwxrwsr-x 4 root lp 1024 Feb 23 23:12 ../ -rw-rx 1 root lp 4 Feb 24 01:39 .seq* -rw-rw 1 daemon lp 86 Feb 24 01:39 cfA029Aa00872 -rw-rw 1 spiegl lp 47978 Feb 24 01:39 dfA029Aa00872 -rw-r--r-- 1 root lp 18 Feb 24 01:39 lock -rw-rw-r-- 1 root lp 25 Feb 24 01:39 status $ ls -lAF `which lpd` `which lprm` -rwsr-sr-x 1 root lp 13157 Nov 24 21:04 /usr/bin/lprm* -rwxr-xr-x 1 root root41417 Nov 24 21:04 /usr/sbin/lpd* Is there anything wrong with the permissions? I didn't change anything after installing Debian 1.2 and updating to Debian 1.4. I have the same problem using the lpr pakage in the rex-fixed. Now I have installed the ii lprng 2.4.2-1lpr/lpd printer spooling system that replaces the lpr pakage and all work fine :). Thanks a lot in advance, Andy. Bye -- Andrea Arcangeli [EMAIL PROTECTED] http://www.imola.queen.it/user/arcangeli/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: lprm says Permission denied (fwd)
On Wed, 26 Feb 1997, Andrea Arcangeli wrote: Hi! something must be wrong with my lpd-setup. When a user starts a print job, s/he can't cancel it anymore. Example: (user 'spiegl') $ lpr abc.txt $ lpq lp is ready and printing Rank Owner Job Files Total Size active spiegl 27 abc.txt 47978 bytes $ lprm 27 cfA027Aa00860: Permission denied cfA027Aa00860: Permission denied $ ls -laF total 54 drwxrwsr-x 2 root lp 1024 Feb 24 01:39 ./ drwxrwsr-x 4 root lp 1024 Feb 23 23:12 ../ -rw-rx 1 root lp 4 Feb 24 01:39 .seq* -rw-rw 1 daemon lp 86 Feb 24 01:39 cfA029Aa00872 -rw-rw 1 spiegl lp 47978 Feb 24 01:39 dfA029Aa00872 -rw-r--r-- 1 root lp 18 Feb 24 01:39 lock -rw-rw-r-- 1 root lp 25 Feb 24 01:39 status $ ls -lAF `which lpd` `which lprm` -rwsr-sr-x 1 root lp 13157 Nov 24 21:04 /usr/bin/lprm* -rwxr-xr-x 1 root root41417 Nov 24 21:04 /usr/sbin/lpd* Is there anything wrong with the permissions? I didn't change anything after installing Debian 1.2 and updating to Debian 1.4. I have the same problem using the lpr pakage in the rex-fixed. I had the same problem, too. lprm can't regonize that the user spiegl is a local user because of a problem with your hostname in /etc/hostname and /etc/hosts. If /etc/hostname looks like your_hostname then your /etc/hosts file should contain a line like this your ip number your_hostname your_hostname.somewhere.com The order of the two names in /etc/hosts is very important. Andreas -- Andreas Nowackmail: Kastanienweg 31, Zi. 3314, D-52074 Aachen, Germany tel: +49-241-876597 \|/ \|/ @'/ ,. \`@email: [EMAIL PROTECTED] /_| \__/ |_\ www: http://www.kawo2.rwth-aachen.de/~nowack \__U_/ fingerprint: B6 1D 0E F6 09 7B A0 EB 38 DB D1 2F C2 F7 48 06 -- Beware of the Penguin! -- Prediction is very difficult, especially of the future. - Niels Bohr -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: lprm says Permission denied (fwd)
On Wed, 26 Feb 1997 15:13:58 +0100 Andreas Nowack ([EMAIL PROTECTED] achen.de) wrote: lprm can't regonize that the user spiegl is a local user because of a problem with your hostname in /etc/hostname and /etc/hosts. If /etc/hostname looks like your_hostname then your /etc/hosts file should contain a line like this your ip number your_hostname your_hostname.somewhere.com The order of the two names in /etc/hosts is very important. This is as simple as that ! This should be put ASAP in the lpd documentation. But doesn't it conflict with the requirement that the official name for a machine (ie FQDN) should be put first in /etc/hosts ? Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: lprm says Permission denied (fwd)
On Wed, 26 Feb 1997, Philippe Troin wrote: On Wed, 26 Feb 1997 15:13:58 +0100 Andreas Nowack ([EMAIL PROTECTED] achen.de) wrote: lprm can't regonize that the user spiegl is a local user because of a problem with your hostname in /etc/hostname and /etc/hosts. If /etc/hostname looks like your_hostname then your /etc/hosts file should contain a line like this your ip number your_hostname your_hostname.somewhere.com The order of the two names in /etc/hosts is very important. This is as simple as that ! This should be put ASAP in the lpd documentation. I agree! After a long time I found the solution somewhere in the debian-bug-list. But doesn't it conflict with the requirement that the official name for a machine (ie FQDN) should be put first in /etc/hosts ? I don't know. Another way is: /etc/hostname: your_hostname.somewhere.com /etc/hosts: your ip number your_hostname.somewhere.com your_hostname The disadvantage (?) of this way is that then the login prompt will look like your_hostname.somewhere.com login: _ Andreas -- Andreas Nowackmail: Kastanienweg 31, Zi. 3314, D-52074 Aachen, Germany tel: +49-241-876597 \|/ \|/ @'/ ,. \`@email: [EMAIL PROTECTED] /_| \__/ |_\ www: http://www.kawo2.rwth-aachen.de/~nowack \__U_/ fingerprint: B6 1D 0E F6 09 7B A0 EB 38 DB D1 2F C2 F7 48 06 -- Beware of the Penguin! -- Prediction is very difficult, especially of the future. - Niels Bohr -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: lprm says Permission denied (fwd)
Philippe Troin ([EMAIL PROTECTED]) wrote on 26 February 1997 09:34: lprm can't regonize that the user spiegl is a local user because of a problem with your hostname in /etc/hostname and /etc/hosts. If /etc/hostname looks like your_hostname then your /etc/hosts file should contain a line like this your ip number your_hostname your_hostname.somewhere.com The order of the two names in /etc/hosts is very important. This is as simple as that ! This should be put ASAP in the lpd documentation. But doesn't it conflict with the requirement that the official name for a machine (ie FQDN) should be put first in /etc/hosts ? Yes. The suggestion is wrong, the suggestion is just a hack. The problem is due to an incoherence between lprm/lpr/lpd. I sent a patch for this last year, I think it was applied but it may have been dropped. I haven't followed lpr*.deb since, because for me it's working and I don't want to touch it ever again. Besides this mess, lpr has security problems as well. The real fix seems to go to lprng. That's the official position of the maintainer as well, as stated in a msg. to this list last year. I'll do it as soon as I have a chance. Carlos -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
