🚀 go-pugleaf

In article <64dl46$vue$1@gidora.kralizec.net.au>,
	nick@zeta.org.au (Nick Andrew) writes:
> In <346935AA.D7F7FA3C@nectar.com.au> Justin Wills <justin@nectar.com.au> writes:
> 
> 
> 
>>> In <3466F13D.5A3B53E@nectar.com.au> Justin Wills <justin@nectar.com.au> writes:
>>> >reboot
>>>
>>> Nope. Major overreaction.
>>>
>>> All it means is there's already a process listening on port 25, on that
>>> IP address (or wildcard address). I.E. sendmail is probably still running.
> 
>>yeah, or that sendmail has died and not released the port, in which case you'll
>>need to reboot
> 
> Nope. On Unix when a process exits the kernel releases all the resources
> which the process held ... including sockets, pipes, open files and
> memory. In the case of TCP sockets, you may have to wait a few seconds
> for the socket to disappear, but it _WILL_ go away. No reboot is required.

There was a problem with ports on which listen had been called in some 
earlier kernel version when the calling process had died. The versions 
where isn the 1.3* range I think. As you say the port should become free but
in fact it did not. This might be the problem here.

-- 
Peter F Bradshaw        | http://www.nautronix.com.au/,  pfb@nautronix.com.au
Nautronix Ltd.          | PGP public key at
108 Marine Terrace      | http://www.iinet.net.au/~pfb/public_key.html
Fremantle, WA, 6160     | "Needs more salt" - Archimedes