Re: [Samba] SOLVED Samba 3.0.0, CUPS support - "Unable to open printcap file cups for read!"
Fran Fabrizio wrote: I'm still having print problems. I'm beginning to wonder if it's my version of CUPS rather than Samba. When I print from my Windows Samba clients, the job shows up in the /var/spool/cups directory, and CUPS web admin says the job completed, but it never prints anything. Same thing from linux samba clients works fine (i.e. if I do 'smbclient //ds119b/myprinter' and then 'print /etc/printcap', it works fine). I had the same probleme here. I use RedHat 8.0, cups 1.1.19 and samba 3.00 (the rpm from samba.org for RedHat8) cups was working fine, but the printcap problem was reported in the samba-logs. So I have got the srpm-samba3.00 from samba.org and rebuild the whole thing - the problem is gone... -- Carsten Buechner EDAG-Wolfsburg| Phone:+49-05361-799181 Schweriner Str. 4 | FAX: +49-05361-799134 38444 Wolfsburg | eMail:[EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SOLVED Samba 3.0.0, CUPS support - "Unable to open printcap file cups for read!"
I'm still having print problems. I'm beginning to wonder if it's my version of CUPS rather than Samba. When I print from my Windows Samba clients, the job shows up in the /var/spool/cups directory, and CUPS web admin says the job completed, but it never prints anything. Same thing from linux samba clients works fine (i.e. if I do 'smbclient //ds119b/myprinter' and then 'print /etc/printcap', it works fine). > CUPS works fine for me here. No dummy printcap needed. Something > else is funny with that configuration. What version of CUPS? I have the following RPMs: cups-devel-1.1.17-13.3.0.3 cups-1.1.17-13.3.0.3 cups-libs-1.1.17-13.3.0.3 Samba 3.0.0 built from source, all standard config settings, on Redhat 9. My entire smb.conf (mostly based off of the samples in the O'Reilly book): [global] netbios name = ds119b workgroup = CISSAMBADOMAIN wins support = yes encrypt passwords = yes domain master = yes local master = yes preferred master = yes os level = 65 security = user domain logons = yes ; roaming profile support logon path = \\%L\profiles\%u\%m logon script = logon.bat logon drive = H: logon home = \\%L\%u\.win_profile\%m time server = yes ; script for adding users add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u # print support printing = cups printcap name = /etc/printcap load printers = yes [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writable = no printable = yes printer admin = root, @ntadmins [netlogon] path = /usr/local/samba/lib/netlogon writable = no browsable = no write list = root fran [profiles] path = /home/samba-ntprof browsable = no writable = yes create mask = 0600 directory mask = 0700 [homes] read only = no browsable = no guest ok = no map archive = yes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SOLVED Samba 3.0.0, CUPS support - "Unable to open printcap file cups for read!"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 10 Dec 2003, Kurt Pfeifle wrote: > Fran Fabrizio wrote: > > >>I have set "Printcap /dev/null" in cupsd.conf and re-started cupsd > >>first then smbd. Guess what? "smbclient -L localhost" still lists all > >>my printers! And I can still print from my Windows apps. (I can't > >>print anymore from OpenOffice, since that one *does* look for a > >>printcap) > > > > > > In desperation I tried "printcap = /etc/printcap" even though the > > HOWTO recommended "printcap = cups" and Kurt's advice above is that > > you could even redirect to /dev/null. Guess what, it worked. At > > least on my install, it seems to require that you do have a real, live > > printcap even for CUPS printing support. I then added another printer > > via the redhat printer config tool, which added it to CUPS. I > > restarted smb and the new printer showed up on my Windows clients. > > So, the residual question is why does it require a real printcap file > > even under CUPS support? > > I think you should submit a bug report to http://bugzilla.samba.org/ CUPS works fine for me here. No dummy printcap needed. Something else is funny with that configuration. - -- cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc "If we're adding to the noise, turn off this song" --Switchfoot (2003) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE/1qm8IR7qMdg1EfYRAqvMAKCZHBM3g2L/elwWBqwUw6Z2eHe91ACgg6QL EubTIqxIz/mBMY4POHUXa0Q= =hLDc -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SOLVED Samba 3.0.0, CUPS support - "Unable to open printcap file cups for read!"
Fran Fabrizio wrote: I have set "Printcap /dev/null" in cupsd.conf and re-started cupsd first then smbd. Guess what? "smbclient -L localhost" still lists all my printers! And I can still print from my Windows apps. (I can't print anymore from OpenOffice, since that one *does* look for a printcap) In desperation I tried "printcap = /etc/printcap" even though the HOWTO recommended "printcap = cups" and Kurt's advice above is that you could even redirect to /dev/null. Guess what, it worked. At least on my install, it seems to require that you do have a real, live printcap even for CUPS printing support. I then added another printer via the redhat printer config tool, which added it to CUPS. I restarted smb and the new printer showed up on my Windows clients. So, the residual question is why does it require a real printcap file even under CUPS support? I think you should submit a bug report to http://bugzilla.samba.org/ The docs don't seem to feel that it should. Now I need to solve the "You do not have sufficient access to your computer to connect to this printer" problem from the Windows clients. :-) Thanks for the help, Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SOLVED Samba 3.0.0, CUPS support - "Unable to open printcap file cups for read!"
> I have set "Printcap /dev/null" in cupsd.conf and re-started cupsd first > then smbd. Guess what? "smbclient -L localhost" still lists all my > printers! And I can still print from my Windows apps. (I can't print > anymore from OpenOffice, since that one *does* look for a printcap) In desperation I tried "printcap = /etc/printcap" even though the HOWTO recommended "printcap = cups" and Kurt's advice above is that you could even redirect to /dev/null. Guess what, it worked. At least on my install, it seems to require that you do have a real, live printcap even for CUPS printing support. I then added another printer via the redhat printer config tool, which added it to CUPS. I restarted smb and the new printer showed up on my Windows clients. So, the residual question is why does it require a real printcap file even under CUPS support? The docs don't seem to feel that it should. Now I need to solve the "You do not have sufficient access to your computer to connect to this printer" problem from the Windows clients. :-) Thanks for the help, Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
