Printcap

[Wade Winright]

Thanks for all of the suggestions, but nothing seemed to work. I've tried
the killall -HUP command and it doesn't read the printcap apparently. I've
tried hitting the Commit Changes to no avail. I've tried skill, no dice.
I've tried logging off the windows client and logging back in, nada. On the
linux side, the printer appears immediately using lpstat, and for printing.
In SWAT if I go to the printers area, the printer is there. When I try to
view the printers from a client, no printer. 
	Does anyone have any more ideas? I am running CUPS if that makes a
difference(don't think it would...).
Thanks again,
Wade

-----Original Message-----
From: Rashkae [mailto:rashkae at wealthmap.ca] 
Sent: Friday, January 11, 2002 10:36 AM
To: Ken Cobler
Cc: Wade Winright; samba at lists.samba.org
Subject: Re: Printcap

On most Linux systems and probably many others, (your mileage may vary)

killall -HUP nmbd
killall -HUP smbd



On Fri, 11 Jan 2002, Ken Cobler wrote:



Wade Winright wrote:

> Hello all,
>
> I have a question that I hope somebody out there can help with. Samba
> doesn't seem to see new printers added to the printcap until it is
> restarted. Am I doing something wrong or is there a way to set samba
> up to check the printcap periodically, or to force it to without
> restarting the service? I have 500 clients that will attach to this
> print server and would like to not have to interrupt there activities
> if I don't have to to add a new printer...
>
> Any ideas would be helpful,
>

I believe the printcap file is only read when the smb connection
starts.  There is a Unix signal you can send to all smbd processes to
tell them to re-read their initialization files (including the
/etc/printcap).

I've found the easiest way to do it is use SWAT and push the button
"Commit changes"  even if there are no changes.  This will properly send
the signal to all smbd processes to access new printcap printers or see
newly added shares.

Ken Cobler