>From time to time someone will comment in this list that their Sambaserver has disappeared from the list of hosts in Network Neighborhood. Browsing the list archive has yet to turn up any good explanation of this phenomenon. I think I have a clue. This morning my server disappeared again. When I checked the process list on the server I noticed that nmbd had been swapped out to disk. The last time the server disappeared nmbd was also swapped out. Once I stopped and restarted the server, it reappeared in NN. Is there a way to prevent nmbd from being swapped out? I looked over the parameters in smb.conf and couldn't find anything there. Is there a way to specify this in the command line that starts nmbd? More importantly, why should it matter whether nmbd is swapped out? Platform: Linux 2.0.35 + Samba 1.9.18p8 (rpm version) but I observed this in earlier 2.0.x kernel versions as well. Peter ----- Peter H. Lemieux Voice: (800) 5-CYWAYS CYWAYS, Incorporated (+1 617 796 8995) 19 Westchester Road Fax: (617) 796-8997 Newton, Massachusetts 02458-2519 USA Web: http://www.cyways.com
Peter, On Wed, 7 Oct 1998 23:20:43 +1000, Peter H. Lemieux wrote:>From time to time someone will comment in this list that their Samba >server has disappeared from the list of hosts in Network Neighborhood. >Browsing the list archive has yet to turn up any good explanation of this >phenomenon. > >I think I have a clue. This morning my server disappeared again. When I >checked the process list on the server I noticed that nmbd had been >swapped out to disk. The last time the server disappeared nmbd was also >swapped out. Once I stopped and restarted the server, it reappeared in NN.>Is there a way to prevent nmbd from being swapped out?>Platform: Linux 2.0.35 + Samba 1.9.18p8This is not a swapping problem! You have to have two nmbd processes running with 1.9.18p8. The one getting swapped out is just the one doing async DNS lookups, it is not the one responsible for a disappearing server. What really happened is as follows: The "father" nmbd died for some reason (nmbd is somewhat unstable in 1.9.18p8, especially when using "remote" keywords). The son process (still living) is no longer active (the father - being dead - is no longer asking him to do DNS lookups) and thus gets swapped out at the next opportunity. Look out for the number of running nmbd processes: If there are two, you will find your server in network neighborhood. If there is only one, it will disappear from the 'hood. Does anyone know if nmbd is more stable in p10? Hasta la vista, Robert -- --------------------------------------------------------------- Robert.Dahlem@frankfurt.netsurf.de Radio Bornheim - 2:2461/332@fidonet +49-69-4930830 (ZyX, V34) 2:2461/326@fidonet +49-69-94414444 (ISDN X.75) ---------------------------------------------------------------
On Wed, 7 Oct 1998 23:20:46 +1000, "Peter H. Lemieux" <phl@cyways.com> wrote:>>From time to time someone will comment in this list that their Samba >server has disappeared from the list of hosts in Network Neighborhood. >Browsing the list archive has yet to turn up any good explanation of this >phenomenon. > >I think I have a clue. This morning my server disappeared again. When I >checked the process list on the server I noticed that nmbd had been >swapped out to disk. The last time the server disappeared nmbd was also >swapped out. Once I stopped and restarted the server, it reappeared in NN.>Is there a way to prevent nmbd from being swapped out?Not really. You could fiddle the code so that every x seconds, every single routine ran (just a little bit of it) provided the whole routine fitted into one page, that would stop a Least Recently Used algorithm from kicking it out. Downside is much greater real memory useage.>I looked over the >parameters in smb.conf and couldn't find anything there. Is there a way >to specify this in the command line that starts nmbd?No it is an OS thing.>More importantly, why should it matter whether nmbd is swapped out?Timing. Disks are slow and it takes time for processes to be swapped back it. A timer may expire in the meanwhile. Another reason is Network Neighborhood sucks, even between Win95 machines. There may be something just slight that upsets it.>Platform: Linux 2.0.35 + Samba 1.9.18p8 (rpm version) but I observed this >in earlier 2.0.x kernel versions as well. > >Peter > >Regards Anthony ==============================================================|'All kids love log!' | | Ren & Stimpy | ===============================================================
Hi, I'd like to know if there is any way to force users to change their passwords periodically. I have a samba server running on Linuz 2.0.35, the workstations (30) run Win95. I mean something simillar to Netware, where the users get a messages "you must change your password, because it expires" or so. Thank you, Peter
I have been disappointed that I can't use Linux+Samba as an alternative to a Win9x or NT server for our GP medical practice. The software we need runs in win9x. We crave stability. But Linux+Samba is just much slower as a file server. I understand that win95 tcp/ip is part of the problem, and it is possible to get MTU-Speed to tweak it, but it just adds to the complexity, and as my patients say "I am just a GP". I notice that when you do a bare install of Win98, that the networking defaults to TCP/IP. Is it possible that Win98 does TCP/IP properly and might be faster than win95 as a tcp/ip workstation client?? Grateful for any feedback. cheers, Hugh Nelson. ---------------------------------------------------- Dr Hugh Nelson <hugh.nelson@ausinfo.com.au> 3 Sir John Overall Dr, Helensvale, QLD 4210, Australia Ph:+61 7 5573 2122 You should use PGP to send and receive encrypted email. To get set up, and to get my PGP encryption key, go to http://www.gpnetwork.net.au I like Pegasus Email with integrated PGP - check out http://community.wow.net/grt/qdpgp.html ------------------------------------------------------------------ This message was spam-checked by an evaluation copy of MailShield. See http://www.mailshield.com for more information.
>Multiple nmbd's: >We are unable to start two nmbd's on separate interfaces to service name >requests on the same server (for cluster failure) - error from second nmbd >log follows: >(Using the '-n' switch and specifying separate smb.conf's and logs) > >--------<output>-------- >bind failed on port 137 socket_addr=0.0.0.0 (Address already in use) >--------<output>-------- > > > >Our Platform Details: >Samba Version = 1.9.18p10 >OS = IBM AIX 4.2.1 >Compiler = IBM C for AIX Version 4.3 > >Use the "socket address = xxx.xxx.xxx.xxx" in smb.conf to setup which address to do the binding to. Also use "interfaces xxx.xxx.xxx.xxx/xxx.xxx.xxx.xxx" for a specific interface. I've done this in both HP-UX and Solaris HA environment and it works fine. Regards, Henrik Henrik Ejderholm Phone: + 46 13 23 52 00 Sectra-Imtec AB Telefax: + 46 13 21 21 85 Teknikringen 2 Internet: he@sectra.se 583 30 Link?ping WWW: http://www.sectra.se