[Samba] Samba 3.0.0, CUPS support - "Unable to open printcap file cups for read!"

[Kurt Pfeifle]

Kurt Pfeifle wrote:
>> [Samba] Samba 3.0.0, CUPS support - "Unable to open printcap file cups 
>> for read!"
>> Fran Fabrizio fran at cis.uab.edu
>> Tue Dec 9 20:06:56 GMT 2003
>>
>>
>> A couple more data points:
>>
>> # smbclient //ds119b/ps4
>> Password:
>> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>> #
> 
> 
> It means Samba doesn't know about a printer share named "ps4"
> (nor a file share of that name)....
> 
>> The syslog shows this as a result:
>>
>> Dec  9 13:46:47 ds119b smbd[21284]: [2003/12/09 13:46:47,
>> 0] printing/pcap.c:pcap_printername_ok(282)
>> Dec  9 13:46:47 ds119b smbd[21284]:   Unable to open printcap file cups
>> for read!
> 
> 
> This message might be bogus in your context and not lead to
> your real problem...
> 
>> Dec  9 13:46:47 ds119b smbd[21284]: [2003/12/09 13:46:47, 0]
>> smbd/service.c:make_connection(850)
>> Dec  9 13:46:47 ds119b smbd[21284]:   ds119b (192.168.2.232) couldn't
>> find service ps4
>>
> 
> See?
> 
>> I can successfully print to this printer from the samba linux host via
>> the standard lpr -Pps4 approach.  I checked my cupsd.conf to make sure
>> it had a Printcap = /etc/printcap and PrintcapFormat = BSD entries and
>> it does. 
> 
> 
> Have you also checked your smb.conf for an entry of
> 
>    "load printers = yes"
> 
> ??
> 
>> The generated /etc/printcap has only one non-comment line,
>> "ps4:". 
> 
> 
> That's OK.
> 
>> -Fran
> 

I forgot: should you have created the "ps4" printer
while smbd was already running, Samba might not yet
know about the printer (Samba bug -- it *should* update
its list of available printer shares just like it does
with file shares....).

Sending a "kill -HUP `pidof smbd`" might help. Or restart
smbd.