Date: Tue, 5 Oct 2004 17:56:52 +0300 (EEST) From: "Perttu Laine" <pepe@kahvipannu.com> To: freebsd-questions@freebsd.org Subject: Re: imapd problem. Message-ID: <1478.62.183.166.174.1096988212.squirrel@ssl.nebula.fi> In-Reply-To: <1096987863.1096.56.camel@prophecy.dyndns.org> References: <4759.62.183.166.174.1096955953.squirrel@ssl.nebula.fi> <1096986652.1096.48.camel@prophecy.dyndns.org> <1450.62.183.166.174.1096987234.squirrel@ssl.nebula.fi> <1096987863.1096.56.camel@prophecy.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Something running under the name of 'inetd' is binding to port 143 on > all inet4 addresses. Either that, or there's a bug in sockstat or the > kernel structures that it manipulates, though I've not seen mention of > that anywhere. Maybe it's an old instance of inetd from a changed > configuration? Perhaps you changed its configuration but forgot to > restart it? Funny. "killall -HUP inetd" helped. I didn't even need to do changes in inetd.conf. I should've just tried to restart it instead of checking config. No idea what I've been doing. Too much vodka perhaps - I'm from Finland you know. ;P Regards, Perttu Laine
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1478.62.183.166.174.1096988212.squirrel>