On Thu, 2004-09-09 at 17:50, Calvin Cannon wrote: > For some reason, it seems that Samba isn't transferring print files to > the print queue. I'm at a bit of a loss because I have another SuSE 9.0 > box configured basically the same way (Different domain name) and it > works great! Basically, both pdf-distiller shares shown below come up > in network neighborhood just fine, and I can connect to the print shares > just fine. Everything works great until I send a job to one of the > print shares. > > When I send a job to either pdf-distiller print share, I get no error > messages, and no PDF file. The [pdf-distiller-debug] share is > configured to add log entries whenever a job is sent. That log file > DOES get updated, but no print file appears in /var/spool/samba/pdf to > be processed by Ghostscript. The spool directory is chmod'ed at 777 so > it shouldn't be a permissions issue, and I'm using the standard Apple > postscript driver on the WinXP side. > > As mentioned earlier, I have another box configured (I think) exactly > the same way and it's working great. I've been ripping my hair out > trying to figure out why this isn't working here. If I had an error > message I would have a place to start, but I don't even have that. > > I appreciate any help you can provide. > > Thanks! > > Calvin Cannon > calvin.cannon@netstruXure.com > > Below is a snippet of code from my smb.conf file. The Global printcap > variable is set to "printcap = cups". > > > ___________________________________________________________________________________ > [printers] > comment = All Printers > path = /var/tmp > printable = yes > create mask = 0600 > browseable = no > guest ok = no > use client driver = yes > > # This share provides printer driver down- and upload in an Windows NT-style > # point-and-print way. For more detailed information consult the Printing > # Support Section of the Samba-HOWTO-Collection. For uploading take extra > # care to add the printer admins to the group lp. > > [print$] > comment = Printer Drivers > path = /var/lib/samba/drivers > write list = @ntadmin root > force group = ntadmin > create mask = 0664 > directory mask = 0775 > browseable = yes > guest ok = no > printable = no > > [pdf-distiller] > comment = PDF Generator - Saves to P: Drive > printing = sysv > printcap = lpstat > path = /var/spool/samba/pdf > printable = Yes > print command = gs -dNOPAUSE -dBATCH -q -sDEVICE=pdfwrite > -sOutputFile=%H/PDF-Distiller/%s.pdf %s; rm %s > > [pdf-distiller-debug] > comment = PDF Generator - Saves to P: Drive > printing = sysv > printcap = lpstat > path = /var/spool/samba/pdf > printable = Yes > print command = echo %T: %u on %m >> > /var/log/samba/PDF-Dilstiller.log; cp %s %H/PDF-Distiller/%s.deleteme ---- Using Samba 3 / RHEL 3 - I have a setup that works and my understanding with Samba 3 is that it is not necessary to have specific sections for the printers at all, they are read by samba directly from cups. Not sure why are you are using printing = cups in [global] and sysv within each printer definition. Thus, I am spooling a bunch of different printers but the only items that I have regarding printing in my smb.conf are: [global] #printer section load printers = yes printing = cups printcap = cups show add printer wizard = yes printer admin = @"Domain Administrators" use client driver = no [printers] comment = Network Printers printer admin = @"Print Operators" path = /home/filesystems/printing/spool/ guest ok = yes printable = yes writable = no read only = Yes [print$] path = /home/filesystems/printing/printers guest ok = Yes browseable = Yes read only = Yes printer admin = root Administrator write list = root create mask = 0664 directory mask = 0775 Craig --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change you mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss