Date: Wed, 26 Jan 2000 11:52:17 +0100 From: "mouss" <usebsd@free.fr> To: "T. William Wells" <bill@twwells.com>, <freebsd-questions@freebsd.org> Subject: RE: Exim Socket Bind Problem Message-ID: <NDBBJDFPGLMLFHLNEEOMEECBDMAA.usebsd@free.fr> In-Reply-To: <86f771$2s5f$1@twwells.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In my viewpoint, this is not abug, minor or not. This is a choice. when you write a program like thisand you call bind() and find that the port is already in use, you have two choices: - abort - sleep and retry The problem with the abort approach is when the program is started by an auxilairy script. There is no user at the console to restart it. so it's better to live with the logs! if you're on the console, you'll still be able to stop the program, check your sockets and other things. otherwise, things will work correctly after some time. well, not completely! if you run the program twice, then the log below will be endless. but this is however better than not having the service started because the last socket data is still not cleaned. A better approcah (this is still my opinion) would be to rerty only a fixed number of time (there is no need to retry or 1 hour!) and stop if bind() fails. not sure if exim does it this way or if it works like the FWTK proxies (which retry for ever). I guess exim was inspired fromthe FWTK and would retry for ever, but didn't see the code (nor do I use it!). regards, mouss T. William Wells wrote > > In article <F16C1C3F6AB8D311998F00C0DF266AE7E1FD@OPTIC>, > Michael Bartlett <cataract@eye2eye.net> wrote: > : I've just got rid of sendmail and slapped Exim onto my FreeBSD > box. It seems > : to work fine except for this which keeps creeping up in my exim_mainlog > : > : 2000-01-20 12:48:11 socket bind() to port 25 for address (any) failed: > : Address already in use: waiting b > : efore trying again > : 2000-01-20 12:48:12 socket bind() to port 25 for address (any) failed: > : Address already in use: waiting b > : bash-2.03# > > I've seen this thing after a reconfiguration -- exim forks a new > process and until the old one dies, you get that message. Other > things might be causing such a fork. I'd regard that as a bug but > a minor one, and one that you should be able to ignore without > harm. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NDBBJDFPGLMLFHLNEEOMEECBDMAA.usebsd>