You choose whether to start from inetd or as a daemon when you install samba. something like:
dpkg --configure samba (UNTESTED) should let you reset it. The reason to run as a daemon instead of from inetd, particularly for nmbd, is that windows clients broadcast name resolution requests *a lot*, particularly if they aren't the browse master (there's a lot more documentation on this at www.samba.org if you're interested). Every time they do, inetd has to start nmbd to answer them (or to decide not to answer). If for some reason you want to run from inetd, you should probably put: os level = 0 preferred master = no in smb.conf, which will at least keep the machine from becoming the browse master for the network. All that said, I don't know why it's failing in the way you posted. This is only theoretical, but I suppose it's possible that nmbd is sending out a broadcast packet when it starts up, which in turn starts it up again, etc., but I have no idea if that's true or even possible. Best, Andy ---------------------------------------------------------------------- Andrew J Perrin - [EMAIL PROTECTED] - http://www.unc.edu/~aperrin Assistant Professor of Sociology, U of North Carolina, Chapel Hill 269 Hamilton Hall, CB#3210, Chapel Hill, NC 27599-3210 USA On Sun, 1 Jul 2001, Andre Alexander Bell wrote: > Hello! > > I've installed the samba packages on my server. > Today someone startet his win95 network client and my server responds with > starting nmbd (as told from inetd.conf) then it gave some exit status 0x1 and > flooded the system. Some time later, I've not been at home during this, the > system wrote that it ran out of memory on the shell and I could not login > anymore. Even not from network. Just reboot helped me out :-(( > This is from /var/log/syslog: > > Jul 1 11:20:22 julia nmbd[2789]: connect from 192.168.76.4 > Jul 1 11:20:22 julia inetd[2757]: /usr/sbin/tcp: exit status 0x1 > ... > repeated many times. then: > Jul 1 11:20:24 julia inetd[2757]: netbios-ns/udp server failing (looping), > service terminated > 10 minutes later the same again... > Jul 1 11:30:35 julia nmbd[2867]: connect from 192.168.76.2 > Jul 1 11:30:35 julia inetd[2757]: /usr/sbin/tcpd: exit status 0x1 > ... > reapeted many times... > > This continues for some hours every 10 minutes... > Then: > > Jul 1 14:02:42 julia kernel: Out of Memory: Killed process 2455 (apache). > even this a few times. But nothing else goes anymore... > > Notice: > - 192.168.76.4 is the win95 compi from my neighbour. > - 192.168.76.2 is my debian/testing box. > - julia is running testing as well. > - both debian/testing boxes do have kernel 2.4.2 > - julia is configured as preferred master, local master and domain master. > - my debian/testing box is not, but has running samba-suite > > What is going wrong here. What do I have to change to get it work properly. > Can anyone advise me somehow? > (btw: in man nmbd under -D stands: running from inetd is possible but not > recommended! Why is it started from inetd in debian? Or am I wrong here?) > > Andre > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
