On Sunday, 1. July 2001 17:10, you wrote:
> I've seen this happen on some systems. It is an inetd bug afaik.
> Do a "killall -9 nmbd" every time you restart inetd, for a workaround.
> Or put it in the /etc/init.d/inetd script, as I did.
Ok, I'll do so...
> > This continues for some hours every
On Sun, Jul 01, 2001 at 04:53:07PM +0200, Andre Alexander Bell wrote:
> 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
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*,
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 wrot
4 matches
Mail list logo