Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
Le Jeudi 3 Octobre 2002 22:37, Buchan Milne a écrit : On 3 Oct 2002, Frederic Soulier wrote: [...] P.S. There will probably be an update for samba in the works, for other reasons ... I suggest we wait for the upcoming 2.2.6 release (should be anytime now) and try again. Regards, Sly -- Sylvestre Taburet - Project Manager - 1024D/030E1B7E Mandrakesoft S.A. - 43, rue d'Aboukir, 75002 Paris - FRANCE +33 (0) 1 40 41 00 41 - http://www.mandrakelinux.com
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
On Thursday 03 October 2002 02:37 pm, Frederic Soulier wrote: testparm returns no error plus this is the same config I used on 8.2 :) Although I'm not having your problem as I dont run winbind, my custom tuned smb.conf that worked even up to rc2 no longer works also. Very starange indeed. I will definately wait till 2.2.6 to see how this goes. Hopefully printing will work agan also. -- -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- Brook Humphrey Mobile PC Medic, 420 1st, Cheney, WA 99004, 509-235-9107 http://www.webmedic.net, [EMAIL PROTECTED], [EMAIL PROTECTED] Holiness unto the Lord -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
Brook Humphrey wrote: On Thursday 03 October 2002 02:37 pm, Frederic Soulier wrote: testparm returns no error plus this is the same config I used on 8.2 :) Although I'm not having your problem as I dont run winbind It wasn't winbind, it was wins , my custom tuned smb.conf that worked even up to rc2 no longer works also. Please define 'no longer works' Very starange indeed. I will definately wait till 2.2.6 to see how this goes. Hopefully printing will work agan also. I have a production machine running 9.0RC2 with samba as wins server, domain controller, serving quite a few printers with downloadeable print drivers, so I fail to see why printing wasn't working. If we had shipped with 2.2.5, it would have had lots of patches (taken from 2.2.6 CVS) to fix printing in 2.2.5 Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
On Friday 04 October 2002 07:44 am, Buchan Milne wrote: Brook Humphrey wrote: Although I'm not having your problem as I dont run winbind It wasn't winbind, it was wins Sorry like I said I don't use it so I got the name wrong. smb.conf that worked even up to rc2 no longer works also. Please define 'no longer works' Well the users can see the shares but not access them. I call that not working. I have it set up to allow anonymous users to my system they are all mapped to an actual user on the system this allows me to admin the file sever as a user on my linux box instead of as root. With the final mandrake 9.0 however, They can't access the shares anymore. It is also set up so that they don't have to login to access the public shares. The strange part is that right after service smb restart the windows boxes can get on and use it for a few minutes and then it starts asking for passwords again. indeed. I will definately wait till 2.2.6 to see how this goes. Hopefully printing will work agan also. I have a production machine running 9.0RC2 with samba as wins server, domain controller, serving quite a few printers with downloadeable print drivers, so I fail to see why printing wasn't working. If we had shipped Please if this is running correctly share your smb.conf with us. At the verry least we may get a few pointers as to how to get it all running like it should be. with 2.2.5, it would have had lots of patches (taken from 2.2.6 CVS) to fix printing in 2.2.5 Ok I know I stated as of rc2 it was still working but now I'm running 9.0 final and not rc2 anymore. I really know nothing about the current samba code and was not trying to say for you guys to patch anything. All I know is that what ever it's doing now does not work. I will note printing does not work using the very tools provided with mandrake. I'm not even using custom samba.conf but the tools mandrake provides. I hove done nothing extra at this point but use the built in tool with the files it produces and I am running 9.0 final. I am using an epson printer that worked before. Where should I look to but to the samba packages. Something is different. I don't know what it is but it's broke if it doesn't work. Now if you have any ideas I will give you any other information you need. Also attached is my current smb.conf produced by the server wizard. -- -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- Brook Humphrey Mobile PC Medic, 420 1st, Cheney, WA 99004, 509-235-9107 http://www.webmedic.net, [EMAIL PROTECTED], [EMAIL PROTECTED] Holiness unto the Lord -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options (perhaps too # many!) most of which are not shown in this example # # Any line which starts with a ; (semi-colon) or a # (hash) # is a comment and is ignored. In this example we will use a # # for commentry and a ; for parts of the config file that you # may wish to enable # # NOTE: Whenever you modify this file you should run the command testparm # to check that you have not made any basic syntactic errors. # #=== Global Settings = [global] # 1. Server Naming Options: # workgroup = NT-Domain-Name or Workgroup-Name workgroup = WORKGROUP # netbios name is the name you will see in Network Neighbourhood, # but defaults to your hostname ; netbios name = name_of_this_server # server string is the equivalent of the NT Description field server string = mandrake # 2. Printing Options: # CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK # (as cups is now used in linux-mandrake 7.2 by default) # if you want to automatically load your printer list rather # than setting them up individually then you'll need this printcap name = lpstat load printers = yes # It should not be necessary to spell out the print system type unless # yours is non-standard. Currently supported print systems include: # bsd, sysv, plp, lprng, aix, hpux, qnx, cups printing = cups # Samba 2.2 supports the Windows NT-style point-and-print feature. To # use this, you need to be able to upload print drivers to the samba # server. The printer admins (or root) may install drivers onto samba. # Note that this feature uses the print$ share, and not the printers share, # so you will need to enable it below. # This parameter works like domain admins: # printer admin = @group user ; printer admin = @adm # 3. Logging Options: # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/log.%m # Put a capping on the size of the log files (in Kb). max log
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
Brook Humphrey wrote:
On Friday 04 October 2002 07:44 am, Buchan Milne wrote:
smb.conf that worked even up to rc2 no longer works also.
Please define 'no longer works'
Well the users can see the shares but not access them. I call that not
working. I have it set up to allow anonymous users to my system they are all
mapped to an actual user on the system this allows me to admin the file sever
as a user on my linux box instead of as root. With the final mandrake 9.0
however, They can't access the shares anymore. It is also set up so that they
don't have to login to access the public shares. The strange part is that
right after service smb restart the windows boxes can get on and use it for a
few minutes and then it starts asking for passwords again.
indeed. I will definately wait till 2.2.6 to see how this goes. Hopefully
printing will work agan also.
I have a production machine running 9.0RC2 with samba as wins server,
domain controller, serving quite a few printers with downloadeable print
drivers, so I fail to see why printing wasn't working. If we had shipped
Please if this is running correctly share your smb.conf with us. At the verry
least we may get a few pointers as to how to get it all running like it
should be.
Depends on what you want it to do. 95% of the configuration I used was
uncommenting stuff that was in the default config. Besides that, one
change for profiles ('writeable = yes'), one change for ntlogon (add
trailing / to netlogon directory).
The rest was adding 3 other shares.
with 2.2.5, it would have had lots of patches (taken from 2.2.6 CVS) to
fix printing in 2.2.5
Ok I know I stated as of rc2 it was still working but now I'm running 9.0
final and not rc2 anymore.
Samba (AFAIK) didn't change between rc2 and final.
I really know nothing about the current samba code
and was not trying to say for you guys to patch anything. All I know is that
what ever it's doing now does not work. I will note printing does not work
using the very tools provided with mandrake.
Printing worked out the box for me ...
I'm not even using custom
samba.conf but the tools mandrake provides.
AFAIK, the closest any of the samba maintainers get to the samba wizard
is sending a good default smb.conf (which the wizard maintainers should
request before each release, since it seems they still have an old one
from 8.2, nothing would have broken, but more examples would be there,
and some more features out-the-box).
I hove done nothing extra at this
point but use the built in tool with the files it produces and I am running
9.0 final. I am using an epson printer that worked before. Where should I
look to but to the samba packages. Something is different. I don't know what
it is but it's broke if it doesn't work. Now if you have any ideas I will
give you any other information you need. Also attached is my current smb.conf
produced by the server wizard.
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command testparm
# to check that you have not made any basic syntactic errors.
#
#=== Global Settings =
[global]
# 1. Server Naming Options:
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = WORKGROUP
# netbios name is the name you will see in Network Neighbourhood,
# but defaults to your hostname
; netbios name = name_of_this_server
# server string is the equivalent of the NT Description field
server string = mandrake
# 2. Printing Options:
# CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK
# (as cups is now used in linux-mandrake 7.2 by default)
# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = lpstat
load printers = yes
correct
# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx, cups
printing = cups
correct, if you can get cups to move paper out the printer.
# Samba 2.2 supports the Windows NT-style point-and-print feature. To
# use this, you need to be able to upload print drivers to the samba
# server. The printer admins (or root) may install drivers onto samba.
# Note that this feature uses the print$ share, and not the
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
On Friday 04 October 2002 08:51 am, Buchan Milne wrote: I was unaware that there were no changes between rc2 and final but something has changed not sure what. This could make thing much harder to work out. Thanks for the help on the default smb.conf but I will attach my real one so you can see what I normally use. But, I have no input on the samba wizard, so it may be more worthwhile to : $ su # kate smb.conf (or preferred editor that has syntax support for smb.conf, such as vim-enhanced) Is there any other besides vim? Well I use gvim but they use the same back-end. and $ man smb.conf Also, you might at least want to read http://ranger.dnsalias.com/mandrake/muo/connect/csamba6.html if you want to run a domain controller, or http://ranger.dnsalias.com/mandrake/muo/connect/csamba5.html if you want to run a domain member (also, if you have two samba servers, one of which is a domain controller). I have read that already to the letter and well it didn't help much. After setting it up exactly like stated I get an error on my xp box about not being able to join the domain. I can't remember the exact error. I did an article on Mandrake Forum about a year ago on printing in samba-2.2.x, which covered most of the printing related stuff (including uploading printer drivers). IMHOSWAT isn't supported by me. Webmin I will tolerate. Linuxconf should be removed./IMHO No worry swat and linuxconf is not tolerated by me either that is why I can't for the life of me figure this out. I've been using this conf file for like two years now with no problem. I use webmin to do the initial setup of my users and turn on the automatic user addition and subtraction if users are added or deleted from my linux box. After that it's all by hand. OK looking back through my smb.conf the one O really use I found the problem. The new mandrake automaticly sets my ip to 192.168.1 for the server doing the connection sharing. I previously had it set to 192.168.0. I had a host allow in my smb.conf set to 192.168.0. for security. Now I added 192.168.1 and 192.168.2 and 127. this fixed it all. Printing is working again. and all my users have access again. The next part is to set up domain controller. Sorry about the false alarm and thanks for listening. Still the default install has changed to this from the default in 8.2. Sorry for the problems. listed below is still my smb.conf and smbusers so others may get use out of it. Domains is next. -- -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- Brook Humphrey Mobile PC Medic, 420 1st, Cheney, WA 99004, 509-235-9107 http://www.webmedic.net, [EMAIL PROTECTED], [EMAIL PROTECTED] Holiness unto the Lord -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options (perhaps too # many!) most of which are not shown in this example # # Any line which starts with a ; (semi-colon) or a # (hash) # is a comment and is ignored. In this example we will use a # # for commentry and a ; for parts of the config file that you # may wish to enable # # NOTE: Whenever you modify this file you should run the command testparm # to check that you have not made any basic syntactic errors. # #=== Global Settings = [global] # 1. Server Naming Options: # workgroup = NT-Domain-Name or Workgroup-Name workgroup = WORKGROUP # netbios name is the name you will see in Network Neighbourhood, # but defaults to your hostname netbios name = server # server string is the equivalent of the NT Description field server string = mandrake # 2. Printing Options: # CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK # (as cups is now used in linux-mandrake 7.2 by default) # if you want to automatically load your printer list rather # than setting them up individually then you'll need this printcap name = lpstat load printers = yes # It should not be necessary to spell out the print system type unless # yours is non-standard. Currently supported print systems include: # bsd, sysv, plp, lprng, aix, hpux, qnx, cups printing = cups # Samba 2.2 supports the Windows NT-style point-and-print feature. To # use this, you need to be able to upload print drivers to the samba # server. The printer admins (or root) may install drivers onto samba. # Note that this feature uses the print$ share, and not the printers share, # so you will need to enable it below. # This parameter works like domain admins: # printer admin = @group user ; printer admin = @adm # 3. Logging Options: # this tells Samba to use a separate log file for each machine # that connects log file
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
On Fri, 4 Oct 2002, Brook Humphrey wrote: Is there any other besides vim? Well I use gvim but they use the same back-end. kate (which was my first suggestion) works fine for me, suiteable if you use KDE, you can even edit smb.conf files remotely with kio_fish ;-). and $ man smb.conf Also, you might at least want to read http://ranger.dnsalias.com/mandrake/muo/connect/csamba6.html if you want to run a domain controller, or http://ranger.dnsalias.com/mandrake/muo/connect/csamba5.html if you want to run a domain member (also, if you have two samba servers, one of which is a domain controller). I have read that already to the letter and well it didn't help much. After setting it up exactly like stated I get an error on my xp box about not being able to join the domain. I can't remember the exact error. Exact error messages help, if you tell me what it is, I can tell you your problem. 60% chance it was Credentials supplied conflict with previously supplied , in which case, blame windows for only being able to have one connection to any machine as a sinlge user, log out, log back in and join the domain as your first action. No worry swat and linuxconf is not tolerated by me either that is why I can't for the life of me figure this out. I've been using this conf file for like two years now with no problem. I use webmin to do the initial setup of my users and turn on the automatic user addition and subtraction if users are added or deleted from my linux box. After that it's all by hand. IMHO, the webmin thing is a hack, pam_smbpasswd might be better (we have considered making it the default, but we can't really). What it does, is change the password in /etc/samba/smbpasswd every time a pam password change is done (ie via passwd or something similar) successfully. OK looking back through my smb.conf the one O really use I found the problem. The new mandrake automaticly sets my ip to 192.168.1 for the server doing the connection sharing. I previously had it set to 192.168.0. I had a host allow in my smb.conf set to 192.168.0. for security. Now I added 192.168.1 and 192.168.2 and 127. this fixed it all. Printing is working again. and all my users have access again. The next part is to set up domain controller. That would have been my next guess. hosts allow is evil (I hope we don't have an example in smb.conf unless it's well documented), since it almost certainly will stuff things up if reverse lookups don't work. Sorry about the false alarm and thanks for listening. Still the default install has changed to this from the default in 8.2. Sorry for the problems. listed below is still my smb.conf and smbusers so others may get use out of it. Domains is next. Glad you came right. Samba set up right (and in conjunction with CUPS) makes life way too easy ;-). Now if only I knew enough about amanda ... Regards, Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
On Wed, 2002-10-02 at 23:08, Todd Lyons wrote: Todd Lyons wrote on Wed, Oct 02, 2002 at 01:57:02PM -0700 : Frederic Soulier wrote on Wed, Oct 02, 2002 at 08:52:39PM +0100 : Why is nmbd started twice? Because a couple name lookups came in between the time that you started it and the time that you did ps ax. There is only one machine on this network... I doubt there's been a name lookup ;) :) Good point! I suggest that you post your smb.conf. There might be I'm such a dummy sometimes. You have wins support turned on. If you turn it off, you'll see that it will only spawn one nmbd. OK fair enough but then there's a problem with service smb stop that cannot handle this 2nd nmbd process correctly. # service smb start Starting SMB services: [OK] Starting NMB services: [OK] # service smb status smbd (pid 4094) is running... nmbd (pid 4105) is running... 4104 (pid ) is running... # service smb stop Shutting down SMB services: [OK] Shutting down NMB services: /etc/init.d/smb: line 253: kill: (4105) No such process # service smb status smbd is stopped nmbd (pid 4180) is running... /Fred
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
On 3 Oct 2002, Frederic Soulier wrote: On Wed, 2002-10-02 at 23:08, Todd Lyons wrote: Todd Lyons wrote on Wed, Oct 02, 2002 at 01:57:02PM -0700 : Frederic Soulier wrote on Wed, Oct 02, 2002 at 08:52:39PM +0100 : Why is nmbd started twice? I'm such a dummy sometimes. You have wins support turned on. If you turn it off, you'll see that it will only spawn one nmbd. Correct, samba normally starts up one nmbd, and an smbd per connection, and en extra nmdb when running WINS. OK fair enough but then there's a problem with service smb stop that cannot handle this 2nd nmbd process correctly. No, there's probably something wrong with your config. # service smb start Starting SMB services: [OK] Starting NMB services: [OK] # service smb status smbd (pid 4094) is running... nmbd (pid 4105) is running... 4104 (pid ) is running... pid 4104 is (probably) the one started by the init script, 4105 is the one spawned later. # service smb stop Shutting down SMB services: [OK] Shutting down NMB services: /etc/init.d/smb: line 253: kill: (4105) No such process Somewhere between here and your previous command, something killed nmbd with pid 4105 # service smb status smbd is stopped nmbd (pid 4180) is running... and for some reason you have another one running which wasn't running before, and shouldn't have been. I have an out-the box 9.0, with no configuration of samba: here I turn on wins support: [root@bgmilne bgmilne]# vi /etc/samba/smb.conf Check what was running before turning on WINS: [root@bgmilne bgmilne]# service smb status smbd (pid 1800) is running... nmbd (pid 1812) is running... and restart it: [root@bgmilne bgmilne]# service smb restart Shutting down SMB services: [ OK ] Shutting down NMB services: [ OK ] Starting SMB services: [ OK ] Starting NMB services: [ OK ] [root@bgmilne bgmilne]# service smb status smbd (pid 16954) is running... nmbd (pid 16965) is running... 16964 (pid ) is running... [root@bgmilne bgmilne]# service smb stop Shutting down SMB services: [ OK ] Shutting down NMB services: [ OK ] [root@bgmilne bgmilne]# service smb status smbd is stopped nmbd is stopped [root@bgmilne bgmilne]# service smb start Starting SMB services: [ OK ] Starting NMB services: [ OK ] [root@bgmilne bgmilne]# service smb status smbd (pid 17067) is running... nmbd (pid 17084) is running... 17077 (pid ) is running... [root@bgmilne bgmilne]# ps -ax|grep [m]bd 17067 ?S 0:00 smbd -D 17077 ?S 0:00 nmbd -D 17084 ?S 0:00 nmbd -D [root@bgmilne bgmilne]# cat /var/run/samba/nmbd.pid 17077 [root@bgmilne bgmilne]# service smb stop Shutting down SMB services: [ OK ] Shutting down NMB services: [ OK ] [root@bgmilne bgmilne]# ps -ax|grep [m]bd [root@bgmilne bgmilne]# I take it you have done standard debugging, which with samba would be: 1)Run testparm to check for errors in your config file. 2)Turn up logging (at least 'log level = 3' in the global section of smb.conf), restart samba, and take a look in /var/log/samba/log.nmbd 3)Checked syslog etc I am 95% sure this is a configuration issue, as we haven't really modified the smb init script in a long time (in fact, I think it may be identical to the one shipped with Mandrake 8.2 in samba-2.2.3a-10mdk, our patch in Mandrake CVS which was applied in 2.2.3a-10mdk: http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/SPECS/samba/Attic/samba-2.2.3a-init.patch went into samba CVS before the release of 2.2.4 http://cvs.samba.org/cgi-bin/cvsweb/samba/packaging/Mandrake/smb.init?only_with_tag=SAMBA_2_2 ) If you still have errors, please either 1)Send your whole smb.conf (to me or [EMAIL PROTECTED], or both) if you made it with some tool like SWAT 2)If you have edited the smb.conf from the one provided by the rpm, you could diff your existing one against the provided winbind version (maybe we need to provide two copies of the default smb.conf in future, Sly?), which has limited known differences. $ diff -u /etc/samba/smb-winbind.conf /etc/samba/smb.conf Also, some idea of your environment would be useful (other samba / windows servers, firewalled or not. P.S. There will probably be an update for samba in the works, for other reasons ... Regards, Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
On Thu, 2002-10-03 at 21:37, Buchan Milne wrote: On 3 Oct 2002, Frederic Soulier wrote: On Wed, 2002-10-02 at 23:08, Todd Lyons wrote: Todd Lyons wrote on Wed, Oct 02, 2002 at 01:57:02PM -0700 : Frederic Soulier wrote on Wed, Oct 02, 2002 at 08:52:39PM +0100 : Why is nmbd started twice? I'm such a dummy sometimes. You have wins support turned on. If you turn it off, you'll see that it will only spawn one nmbd. Correct, samba normally starts up one nmbd, and an smbd per connection, and en extra nmdb when running WINS. Well, My box at home has this pbm, my box at work does not... Main diff is my box at home is a 2 CPUs P3 custom built (ran LM 8.0, 8,1, 8.2 and 9.0) and my box at work is 1 CPU P3 (Dell Dimension 4100) OK fair enough but then there's a problem with service smb stop that cannot handle this 2nd nmbd process correctly. No, there's probably something wrong with your config. testparm returns no error plus this is the same config I used on 8.2 :) # service smb start Starting SMB services: [OK] Starting NMB services: [OK] # service smb status smbd (pid 4094) is running... nmbd (pid 4105) is running... 4104 (pid ) is running... pid 4104 is (probably) the one started by the init script, 4105 is the one spawned later. # service smb stop Shutting down SMB services: [OK] Shutting down NMB services: /etc/init.d/smb: line 253: kill: (4105) No such process Somewhere between here and your previous command, something killed nmbd with pid 4105 # service smb status smbd is stopped nmbd (pid 4180) is running... and for some reason you have another one running which wasn't running before, and shouldn't have been. I have an out-the box 9.0, with no configuration of samba: here I turn on wins support: [root@bgmilne bgmilne]# vi /etc/samba/smb.conf Check what was running before turning on WINS: [root@bgmilne bgmilne]# service smb status smbd (pid 1800) is running... nmbd (pid 1812) is running... and restart it: [root@bgmilne bgmilne]# service smb restart Shutting down SMB services: [ OK ] Shutting down NMB services: [ OK ] Starting SMB services: [ OK ] Starting NMB services: [ OK ] [root@bgmilne bgmilne]# service smb status smbd (pid 16954) is running... nmbd (pid 16965) is running... 16964 (pid ) is running... [root@bgmilne bgmilne]# service smb stop Shutting down SMB services: [ OK ] Shutting down NMB services: [ OK ] [root@bgmilne bgmilne]# service smb status smbd is stopped nmbd is stopped [root@bgmilne bgmilne]# service smb start Starting SMB services: [ OK ] Starting NMB services: [ OK ] [root@bgmilne bgmilne]# service smb status smbd (pid 17067) is running... nmbd (pid 17084) is running... 17077 (pid ) is running... [root@bgmilne bgmilne]# ps -ax|grep [m]bd 17067 ?S 0:00 smbd -D 17077 ?S 0:00 nmbd -D 17084 ?S 0:00 nmbd -D [root@bgmilne bgmilne]# cat /var/run/samba/nmbd.pid 17077 [root@bgmilne bgmilne]# service smb stop Shutting down SMB services: [ OK ] Shutting down NMB services: [ OK ] [root@bgmilne bgmilne]# ps -ax|grep [m]bd [root@bgmilne bgmilne]# Just tried with smb.conf from LM9.0 installation with no modif. Only 1 smbd and 1 nmbd process created. Then uncommented wins support = yes and restarted smb, this triggered exactly the same pbm... bogus nmbd process. I take it you have done standard debugging, which with samba would be: 1)Run testparm to check for errors in your config file. 2)Turn up logging (at least 'log level = 3' in the global section of smb.conf), restart samba, and take a look in /var/log/samba/log.nmbd 3)Checked syslog etc I am 95% sure this is a configuration issue, as we haven't really modified the smb init script in a long time (in fact, I think it may be identical to the one shipped with Mandrake 8.2 in samba-2.2.3a-10mdk, our patch in Mandrake CVS which was applied in 2.2.3a-10mdk: http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/SPECS/samba/Attic/samba-2.2.3a-init.patch went into samba CVS before the release of 2.2.4 http://cvs.samba.org/cgi-bin/cvsweb/samba/packaging/Mandrake/smb.init?only_with_tag=SAMBA_2_2 ) If you still have errors, please either 1)Send your whole smb.conf (to me or [EMAIL PROTECTED], or both) if you made it with some tool like SWAT 2)If you have edited the smb.conf from the one provided by the rpm, you could diff your existing one against the provided winbind version (maybe
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
Frederic Soulier wrote on Wed, Oct 02, 2002 at 06:06:09PM +0100 : # ps aux shows 1 smbd -D process and 2 nmbd -D processes. If you actually login about 20 people to the Samba server, you'll see 20 smbd processes. Why is nmbd started twice? Because a couple name lookups came in between the time that you started it and the time that you did ps ax. Blue skies... Todd -- MandrakeSoft USA http://www.mandrakesoft.com Mandrake: An amalgam of good ideas from RedHat, Debian, and MandrakeSoft. All in all, IMHO, an unbeatable combination. --Levi Ramsey on Cooker ML Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-16mdk msg77853/pgp0.pgp Description: PGP signature
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
Frederic Soulier wrote on Wed, Oct 02, 2002 at 08:52:39PM +0100 : Why is nmbd started twice? Because a couple name lookups came in between the time that you started it and the time that you did ps ax. There is only one machine on this network... I doubt there's been a name lookup ;) :) Good point! I suggest that you post your smb.conf. There might be something in there that's making it do this. I do not see this behavior on my system, but I would like to try with your smb.conf to see if it causes it. Just attach it to a reply email. Blue skies... Todd -- Todd Lyons -- MandrakeSoft, Inc. http://www.mandrakesoft.com/ UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-16mdk msg77867/pgp0.pgp Description: PGP signature
Re: [Cooker] LM9.0: Samba (1 smbd process, 2 nmbd processes)
Todd Lyons wrote on Wed, Oct 02, 2002 at 01:57:02PM -0700 : Frederic Soulier wrote on Wed, Oct 02, 2002 at 08:52:39PM +0100 : Why is nmbd started twice? Because a couple name lookups came in between the time that you started it and the time that you did ps ax. There is only one machine on this network... I doubt there's been a name lookup ;) :) Good point! I suggest that you post your smb.conf. There might be I'm such a dummy sometimes. You have wins support turned on. If you turn it off, you'll see that it will only spawn one nmbd. Blue skies... Todd -- MandrakeSoft USA http://www.mandrakesoft.com Never take no as an answer from someone who's not authorized to say yes. --Ben Reser on Cooker ML Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-16mdk msg77882/pgp0.pgp Description: PGP signature
