I am really quite puzzled as to why I have to edit smb.conf every time I want to print to the FreeBSD machine from Win2K. (Running FBSD 4.7, samba 2.2.7 and cups 1.1.15.1_4. When I log onto FBSD with username, password, I see the folders for the printers, home, tmp, etc. but no printer. (Only 1 installed - Epson Stylus Color 900). I can access the shares on FBSD from Win2k, but there is no printer. If I edit smb.conf, with insignificant changes not affecting the printer sections (Printers and Print$) the printer appears. As a side note, I think that the Printer$ section may not be needed if I do not install any Windows or other special drivers - frankly, I don't know why it is even there :(( It appears that editing smb.conf forces the smbd program to reread the smb.conf file. But why would it not have read it correctly in the first place? Anyone out there understand this? thanks in advance PJ
You could just kill sighup smbdprocessid On linux it is kill -1. You might post your smb.conf. Have you run testparm? Joel On Tue, Dec 10, 2002 at 06:45:44PM -0500, pippo@bellnet.ca wrote:> I am really quite puzzled as to why I have to edit smb.conf every time I > want to print to the FreeBSD machine from Win2K. (Running FBSD 4.7, samba > 2.2.7 and cups 1.1.15.1_4. > When I log onto FBSD with username, password, I see the folders for the > printers, home, tmp, etc. but no printer. (Only 1 installed - Epson Stylus > Color 900). > I can access the shares on FBSD from Win2k, but there is no printer. > If I edit smb.conf, with insignificant changes not affecting the printer > sections (Printers and Print$) the printer appears. > As a side note, I think that the Printer$ section may not be needed if I do > not install any Windows or other special drivers - frankly, I don't know > why it is even there :(( > It appears that editing smb.conf forces the smbd program to reread the > smb.conf file. But why would it not have read it correctly in the first place? > Anyone out there understand this? > thanks in advance > PJ > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba
At 07:51 PM 12/10/2002 -0500, you wrote:>You could just kill sighup smbdprocessid >On linux it is kill -1.Why would I do that? The machine is running, smbd is running; I just want to log on and print. :)) I don't want to go through the contortions of shutting a process down and then restarting it just to do a simple function (printing).>You might post your smb.conf. >Have you run testparm?Of course, I did. :)) As a matter of fact, I even deleted the [print$] section in my latest edit and print saga... I'll post the smb.conf file tomorrow. It's been too long a day... PJ>Joel > > >On Tue, Dec 10, 2002 at 06:45:44PM -0500, pippo@bellnet.ca wrote: > > I am really quite puzzled as to why I have to edit smb.conf every time I > > want to print to the FreeBSD machine from Win2K. (Running FBSD 4.7, samba > > 2.2.7 and cups 1.1.15.1_4. > > When I log onto FBSD with username, password, I see the folders for the > > printers, home, tmp, etc. but no printer. (Only 1 installed - Epson Stylus > > Color 900). > > I can access the shares on FBSD from Win2k, but there is no printer. > > If I edit smb.conf, with insignificant changes not affecting the printer > > sections (Printers and Print$) the printer appears. > > As a side note, I think that the Printer$ section may not be needed if > I do > > not install any Windows or other special drivers - frankly, I don't know > > why it is even there :(( > > It appears that editing smb.conf forces the smbd program to reread the > > smb.conf file. But why would it not have read it correctly in the first > place? > > Anyone out there understand this? > > thanks in advance > > PJ > > > > > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: http://lists.samba.org/mailman/listinfo/samba