Printcap

[Wade Winright]

Thanks for the input. I only have on smb.conf on the system. Double-checked
just to be sure. Smbclient command showed the same thing as Win2k clients. I
know I can restart the smb service to make it see printcap (lpstat) but it
will kill all other print jobs in the process. So, I need to find a way to
get samba to reread the printcap without restarting. 
I hope there is a way to do this....

-----Original Message-----
From: Ken Cobler [mailto:kcobler at coblercorp.com] 
Sent: Friday, January 11, 2002 12:27 PM
To: Wade Winright
Subject: Re: Printcap



Wade Winright wrote:

> 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
>

I don't know about CUPS, but, I do know that printers available from
/etc/printcap are reported by Samba.  The only thing you might want to check
is
your Samba version and your SWAT version.  Are they both pointing to or
reading
from the same smb.conf file ?  Sometimes people use one version that reads
from
/etc/samba/smb.conf and another they built that points to
/usr/local/samba/lib/smb.conf

After you make a change to /etc/printcap, you are restarting your lp daemon
process ?  You mention lpstat, which is a SysV lp daemon.  I'm used to Linux
where you restart lpd after making changes to /etc/printcap.

Once you restart lp daemon and then SWAT commit changes, you should be able
from the console type: "smbclient -L //Server -U root", type in the root
password and see the new printer you added in the list (without having to go
to
Windows workstation to see if it worked).

Just a couple of thoughts.

Ken Cobler