samba - Oct 1998 - inetd and Solaris

Environment: Solaris 2.5.1 Samba 1.9.18p3

We run samba from inetd (no special reason - just how its been done in the 
past).  Then on one server we got masses of Samba daemons running (up to 40 as 
a time trying to run - load average 40+!), giving following complaints:


Sep 28 14:39:06 zeus.brunel.ac.uk smbd[10728]: standard input is not a socket, 
a
ssuming -D option
Sep 28 14:39:06 zeus.brunel.ac.uk smbd[10742]: bind failed on port 139 
socket_ad
dr=0.0.0.0 (Address already in use)

... the second error message is because inetd has the socket.  The problem 
went away when I killed & restarted inetd - thus allowing one of the many
smbd
to grab the socket as deamon (verified with lsof).

I speculate that the problem was due to the Solaris inetd property of limiting 
40 connection in 60 seconds to a service - not much if whole classroom of NT 
machines starts up.  I do not see why this should lead to lots of smbd's
being
started with stdin not a socket.

Does anyone have any further explanation?

Should Solaris users be discouraged from using inetd to start smbd?
BTW I am aware of the -r option to inetd.

-- 
-----------------------------------------------------------------------------
| Peter Polkinghorne, Computer Centre, Brunel University, Uxbridge, UB8 3PH,|
| Peter.Polkinghorne@brunel.ac.uk   +44 1895 274000 x2561       UK          |
-----------------------------------------------------------------------------

In a message dated: Fri, 02 Oct 1998 00:08:03 +1000
Peter Polkinghorne said:
>Should Solaris users be discouraged from using inetd to start smbd?
>BTW I am aware of the -r option to inetd.
I wouldn't do it just because of the problems you're experiencing. 
Samba
is one of those daemons that a lot of people are likely to hit
simultaneously, and in great quantities. Why start many instances of smbd
and nmbd when only 1 of each will do.  Write a small startup script for it
in /etc/rc2.d and let it start at boot time.

Just my $.02

-- 

Seeya,
Paul
----
plussier@baynetworks.com
Broadband Technology Division - Bay Networks (now a Nortel Company, Eh! :)

	If you're not having fun, you're not doing it right!