All, I have the following in my smb.comf for printing commands... # NOTE: If you have a BSD-style print system there is no need to # specifically define each individual printer [printers] comment = All Printers path = /var/spool/samba browseable = no print ok = yes print command = /usr/bin/lpr -P%p -r %s lpq command = /usr/bin/lpq -P%p lprm command = /usr/bin/lprm -P%p %j lppause command = /usr/sbin/lpc hold %p %j lpresume command = /usr/sbin/lpc release %p %j queuepause command = /usr/sbin/lpc -P%p stop queueresume command = /usr/sbin/lpc -P%p start I got this from a tech guy from Red Hat. When I try to pause a print job, it says "You do not have sufficient privaliges to modify this job." I did a chmod 777 on /usr/bin and /usr/sbin to no avail. Red Hat support (oxymoron) says that they have no idea as to what would be causing this (windoze or linux). Any ideas? Has anyone ran into this? System config is Red Hat 7.1 with samba 2.2.2 Cheers, Tony ------------------------------- Tony Ricker Technology Coordinator SLUCare - P.M.O. St. Louis University Phone: 314.977.6844 E-mail: rickera2@slu.edu ------------------------------- "In the beginners mind, there are many possibilities. In the experts mind, there are few" - Shunryu Suzuki ------------------------------- "Think Different"
what's your admin users set to?? ----- Original Message ----- From: "Tony Ricker" <rickera2@SLU.EDU> To: "Samba NT-Dom" <samba-ntdom@lists.samba.org>; "Samba" <samba@lists.samba.org> Sent: November 26, 2001 10:48 AM Subject: printing error All, I have the following in my smb.comf for printing commands... # NOTE: If you have a BSD-style print system there is no need to # specifically define each individual printer [printers] comment = All Printers path = /var/spool/samba browseable = no print ok = yes print command = /usr/bin/lpr -P%p -r %s lpq command = /usr/bin/lpq -P%p lprm command = /usr/bin/lprm -P%p %j lppause command = /usr/sbin/lpc hold %p %j lpresume command = /usr/sbin/lpc release %p %j queuepause command = /usr/sbin/lpc -P%p stop queueresume command = /usr/sbin/lpc -P%p start I got this from a tech guy from Red Hat. When I try to pause a print job, it says "You do not have sufficient privaliges to modify this job." I did a chmod 777 on /usr/bin and /usr/sbin to no avail. Red Hat support (oxymoron) says that they have no idea as to what would be causing this (windoze or linux). Any ideas? Has anyone ran into this? System config is Red Hat 7.1 with samba 2.2.2 Cheers, Tony ------------------------------- Tony Ricker Technology Coordinator SLUCare - P.M.O. St. Louis University Phone: 314.977.6844 E-mail: rickera2@slu.edu ------------------------------- "In the beginners mind, there are many possibilities. In the experts mind, there are few" - Shunryu Suzuki ------------------------------- "Think Different" -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
What permissions do you have on /var/spool/samba? -----Original Message----- From: Tony Ricker [mailto:rickera2@SLU.EDU] Sent: Monday, November 26, 2001 12:49 PM To: Samba NT-Dom; Samba Subject: printing error All, I have the following in my smb.comf for printing commands... # NOTE: If you have a BSD-style print system there is no need to # specifically define each individual printer [printers] comment = All Printers path = /var/spool/samba browseable = no print ok = yes print command = /usr/bin/lpr -P%p -r %s lpq command = /usr/bin/lpq -P%p lprm command = /usr/bin/lprm -P%p %j lppause command = /usr/sbin/lpc hold %p %j lpresume command = /usr/sbin/lpc release %p %j queuepause command = /usr/sbin/lpc -P%p stop queueresume command = /usr/sbin/lpc -P%p start I got this from a tech guy from Red Hat. When I try to pause a print job, it says "You do not have sufficient privaliges to modify this job." I did a chmod 777 on /usr/bin and /usr/sbin to no avail. Red Hat support (oxymoron) says that they have no idea as to what would be causing this (windoze or linux). Any ideas? Has anyone ran into this? System config is Red Hat 7.1 with samba 2.2.2 Cheers, Tony ------------------------------- Tony Ricker Technology Coordinator SLUCare - P.M.O. St. Louis University Phone: 314.977.6844 E-mail: rickera2@slu.edu ------------------------------- "In the beginners mind, there are many possibilities. In the experts mind, there are few" - Shunryu Suzuki ------------------------------- "Think Different" -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Just so you know. I have the same problem. I can lprm the jobs. lpc is suid, like lprm. I am right now reading man lpc. There are files which control who can access the printer queue in there. I'll race you to the answer. Joel On Mon, Nov 26, 2001 at 12:48:41PM -0600, Tony Ricker wrote:> All, > I have the following in my smb.comf for printing commands... > > # NOTE: If you have a BSD-style print system there is no need to > # specifically define each individual printer > [printers] > comment = All Printers > path = /var/spool/samba > browseable = no > print ok = yes > print command = /usr/bin/lpr -P%p -r %s > lpq command = /usr/bin/lpq -P%p > lprm command = /usr/bin/lprm -P%p %j > lppause command = /usr/sbin/lpc hold %p %j > lpresume command = /usr/sbin/lpc release %p %j > queuepause command = /usr/sbin/lpc -P%p stop > queueresume command = /usr/sbin/lpc -P%p start > > I got this from a tech guy from Red Hat. When I try to pause a print > job, it says "You do not have sufficient privaliges to modify this job." > I did a chmod 777 on /usr/bin and /usr/sbin to no avail. Red Hat support > (oxymoron) says that they have no idea as to what would be causing this > (windoze or linux). Any ideas? Has anyone ran into this? System config > is Red Hat 7.1 with samba 2.2.2 > > Cheers, > > Tony > ------------------------------- > Tony Ricker > Technology Coordinator > SLUCare - P.M.O. > St. Louis University > Phone: 314.977.6844 > E-mail: rickera2@slu.edu > ------------------------------- > "In the beginners mind, there > are many possibilities. In the > experts mind, there are few" > - Shunryu Suzuki > ------------------------------- > "Think Different" > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba
Well, the original post drifted away, so I added a new name, hoping this won't be overlooked. This is due to two things: First, when lpd starts up, it reads lpd.perms, which may reside in /etc/lpd.perms, other etc locations, and/or in the print queue itself. lpd.perms is dense, beyond me for now, but, if you make it a one line configuration file: DEFAULT ACCEPT then you allow everyone to access the full range of lpc and other commands. Not very secure but this is troubleshooting. Make sure your firewall is up. Second, unlike linux, which allows everyone then to alter print jobs in the queue, windows only allows the owner of the file to alter the print job, even with DEFAULT ACCEPT as above. Ergo, in a windows environment, this DEFAULT ACCEPT may not be too serious. A windows user cannot for example cancel any print jobs other than the ones he owns under the name he logged into windows with, and, he cannot stop the queue, etc, as far as I can see. (I would definitely check this out for yourself. By day I examine gallbladders for a living.) So, if the user name in windows is the same as the user name that samba is working with, and I have made lpd.perms a one line open door as above, then I can pause and resume jobs. Yeaah!. However, if the windows user name is different from the user name in samba, and it will be different if you have a guest login like ftp, then the windows user cannot pause and resume jobs. Windows won't let them. Now, there may be errors in this explanation, since I cannot exhaustively try every combination of variables and still keep my day job, but, that is what I have done and it works. It is somewhat shocking that a linux tech support hotline wouldn't have thought of lpd.perms as the reason for this. After all, they do this for their bread and butter. Joel On Mon, Nov 26, 2001 at 12:48:41PM -0600, Tony Ricker wrote:> All, > I have the following in my smb.comf for printing commands... > > # NOTE: If you have a BSD-style print system there is no need to > # specifically define each individual printer > [printers] > comment = All Printers > path = /var/spool/samba > browseable = no > print ok = yes > print command = /usr/bin/lpr -P%p -r %s > lpq command = /usr/bin/lpq -P%p > lprm command = /usr/bin/lprm -P%p %j > lppause command = /usr/sbin/lpc hold %p %j > lpresume command = /usr/sbin/lpc release %p %j > queuepause command = /usr/sbin/lpc -P%p stop > queueresume command = /usr/sbin/lpc -P%p start > > I got this from a tech guy from Red Hat. When I try to pause a print > job, it says "You do not have sufficient privaliges to modify this job." > I did a chmod 777 on /usr/bin and /usr/sbin to no avail. Red Hat support > (oxymoron) says that they have no idea as to what would be causing this > (windoze or linux). Any ideas? Has anyone ran into this? System config > is Red Hat 7.1 with samba 2.2.2 > > Cheers, > > Tony
I forgot one item. If the print job is stalled (eg. The printer was turned off and it is the first job in the queue) then pausing may not work properly. Joel On Thu, Nov 29, 2001 at 10:28:02AM -0600, Tony Ricker wrote:> Joel, > I was able to implement your fix, thanks. I will play with the original > lpd.perms and share any headway I make. I thank you for your help. > > Cheers, > > Tony > > Joel Hammer wrote: > > > > Well, the original post drifted away, so I added a new name, hoping this > > won't be overlooked. > > This is due to two things: > > First, when lpd starts up, it reads lpd.perms, which may reside in > > /etc/lpd.perms, other etc locations, and/or in the print queue itself. > > lpd.perms is dense, beyond me for now, but, if you make it a one line > > configuration file: > > DEFAULT ACCEPT > > then you allow everyone to access the full range of lpc and other commands. > > Not very secure but this is troubleshooting. Make sure your firewall is up. > > Second, unlike linux, which allows everyone then to alter print jobs in the > > queue, windows only allows the owner of the file to alter the print job, > > even with DEFAULT ACCEPT as above. Ergo, in a windows environment, this > > DEFAULT ACCEPT may not be too serious. A windows user cannot for example > > cancel any print jobs other than the ones he owns under the name he logged > > into windows with, and, he cannot stop the queue, etc, as far as I can see. > > (I would definitely check this out for yourself. By day I examine > > gallbladders for a living.) > > So, if the user name in windows is the same as the user name that samba is > > working with, and I have made lpd.perms a one line open door as above, > > then I can pause and resume jobs. Yeaah!. > > However, if the windows user name is different from the user name in samba, > > and it will be different if you have a guest login like ftp, then the windows > > user cannot pause and resume jobs. Windows won't let them. > > Now, there may be errors in this explanation, since I cannot exhaustively > > try every combination of variables and still keep my day job, but, that is > > what I have done and it works. > > It is somewhat shocking that a linux tech support hotline wouldn't have > > thought of lpd.perms as the reason for this. After all, they do this for > > their bread and butter. > > Joel > > > > On Mon, Nov 26, 2001 at 12:48:41PM -0600, Tony Ricker wrote: > > > All, > > > I have the following in my smb.comf for printing commands... > > > > > > # NOTE: If you have a BSD-style print system there is no need to > > > # specifically define each individual printer > > > [printers] > > > comment = All Printers > > > path = /var/spool/samba > > > browseable = no > > > print ok = yes > > > print command = /usr/bin/lpr -P%p -r %s > > > lpq command = /usr/bin/lpq -P%p > > > lprm command = /usr/bin/lprm -P%p %j > > > lppause command = /usr/sbin/lpc hold %p %j > > > lpresume command = /usr/sbin/lpc release %p %j > > > queuepause command = /usr/sbin/lpc -P%p stop > > > queueresume command = /usr/sbin/lpc -P%p start > > > > > > I got this from a tech guy from Red Hat. When I try to pause a print > > > job, it says "You do not have sufficient privaliges to modify this job." > > > I did a chmod 777 on /usr/bin and /usr/sbin to no avail. Red Hat support > > > (oxymoron) says that they have no idea as to what would be causing this > > > (windoze or linux). Any ideas? Has anyone ran into this? System config > > > is Red Hat 7.1 with samba 2.2.2 > > > > > > Cheers, > > > > > > Tony > > > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: http://lists.samba.org/mailman/listinfo/samba > > -- > ------------------------------- > Tony Ricker > Technology Coordinator > SLUCare - P.M.O. > St. Louis University > Phone: 314.977.6844 > E-mail: rickera2@slu.edu > ------------------------------- > "In the beginners mind, there > are many possibilities. In the > experts mind, there are few" > - Shunryu Suzuki > ------------------------------- > "Think Different"