[OpenIndiana-discuss] smb/server not getting a socket - service fails

[Harry Putnam]

Jim Klimov <jimklimov at cos.ru> writes:

[...]

>
> Did you test it at "face value" - i.e. that you have some daemon
> already serving cifs (i.e. "samba" and "smb/server" both enabled)
> or otherwise holding the ip:port in question?

Ahhh ..errm... no.  

[...]

Marion Hakanson <hakansom at ohsu.edu> writes:

[...]

Marion H wrote:
> Harry,
>
> This error message in general means that the socket is already in use.
> In practice, it usually means the service is already (still?) running,
> but it could also mean that something else (maybe "samba") is making
> use of the socket.
>
> You may find a clue using "netstat -a" (or "-an"), and look for ports
> 445, 137, 138, 139 being in use.  445 would be used by both the
> kernel CIFS (smb/server) and by samba, for example.  So only one such
> service could be running at a time.

Egad... It was something simple after all.  You both guessed it.  I
foolishly had them both starting on boot.

I disabled them both, then enabled smb/server.... it started cleanly.

Man, I had already decided that error message was cloaking something
much deeper and complicated beyond all reason...

Sorry to have wasted both of your times.  But at least your clues made
me get my thinking cap on... I should have thought of
netstat... thanks for the tips... both of you.