Hi there, I'm having an unusual problem. We are running Samba 1.9.18p8 on an Intel PII running Unixware 2.1.2. Recently recently we've been seeing problems with samba printing. We've narrowed it down to a problem with the "Print Command" function in smb.conf. At some point, whatever is configured as the "Print Command", never gets executed. Even if the print command is to just copy the print file to the /tmp directory (which is what I ended up doing to try to isolate the problem away from system printing issues). The odd thing is that if I start samba with a debug of 5, it -shows- the command being issued in the log files. The following shows that the command to move the print file to the /tmp directory was run: Running the command `cat /home/public/spool/drew.b006Rx | lp -d hp3main' gave 0 1999/03/24 11:07:05 tdrew closed file drew.b006Rx (numopen=0) I assume that the "gave 0" means that the command returned a "true" exit status. The command never actually executes. The solution has been to restart samba. That would work for a few minutes, then I would have to do it again. Also note that all of the other samba services continued to work without any problems. Does anyone have any suggestions as to what might be causing this problem? Drew
At 09:32 AM 3/24/99 -0800, Herb Lewis wrote:>make sure you specify the full path to your print command. The >environment in samba may not find the command. >Hmm. I tried this, but a few hours later, it happened again. Like I said, it works fine for a while. Usually I can just restart samba, and it will continue to work., then it dies. I am seeing a lot of "lpq command" instances in the log. More than the "Print command". Do you think I need to increase my "lpq cache time"? Drew> >Drew Morone wrote: >> >> Hi there, >> >> I'm having an unusual problem. >> We are running Samba 1.9.18p8 on an Intel PII running Unixware 2.1.2. >> Recently recently we've been seeing problems with samba printing. >> We've narrowed it down to a problem with the "Print Command" function in >> smb.conf. >> At some point, whatever is configured as the "Print Command", never gets >> executed. Even if the print command is to just copy the print file to the >> /tmp directory (which is what I ended up doing to try to isolate the problem >> away from system printing issues). The odd thing is that if I start samba >> with a debug of 5, it -shows- the command being issued in the log files. The >> following shows that the command to move the print file to the /tmp >> directory was run: >> >> Running the command `cat /home/public/spool/drew.b006Rx | lp -d hp3main'gave 0>> 1999/03/24 11:07:05 tdrew closed file drew.b006Rx (numopen=0) >> >> I assume that the "gave 0" means that the command returned a "true" exit >> status. The command never actually executes. >> >> The solution has been to restart samba. That would work for a few minutes, >> then I would have to do it again. >> >> Also note that all of the other samba services continued to work without any >> problems. >> >> Does anyone have any suggestions as to what might be causing this problem? >> >> Drew > >-- >=====================================================================>Herb Lewis Silicon Graphics >Technical Marketing 2011 N Shoreline Blvd >Network Systems Division Mountain View, CA 94043 >herb@sgi.com Tel: 650-933-2177 >http://www.sgi.com Fax: 650-932-2177 >=====================================================================>
Hi there, I have problems with using of "print command", when configuring printers. I want to log all jobs (so in fact, I don't want to print it, I just want to save it to database). But it looks to me that this command has no efect. I will explain it. For example, I set print command to: echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s (in globals and printer settings) The job is printed, but not loged in /tmp/print.log (file has permission to read,write for all) When I set print command just to cp %s /tmp/testprint.log Then the file is again only printed and not logged (there is _no_ lpr command now) I have tried to configure new printer with no linux printer defined. But the job allways hang on Win machine then (I think thats because lpr fails - but again I have switched lpr command to cp %s /tmp/testprint.log and nothing happend). Can you send me some ideas how to solve this, please. Martin Novak PS: SERVER SOFTWARE: RedHat 7.3, Samba 2.2.8 (I had 2.2.7 before and this problem force me to upgrade), printing via lprng printing from Windows 2000