From owner-freebsd-questions Sun Jan 23 7:38:38 2000 Delivered-To: freebsd-questions@freebsd.org Received: from twwells.com (mtholly-pri-13.ppp.netaxs.com [207.8.237.31]) by hub.freebsd.org (Postfix) with SMTP id 030A015797 for ; Sun, 23 Jan 2000 07:38:06 -0800 (PST) (envelope-from news@twwells.com) Received: from news by twwells.com with local (Exim 1.71 #2) id 12CP5U-000OhY-00; Sun, 23 Jan 2000 10:38:00 -0500 From: bill@twwells.com (T. William Wells) To: freebsd-questions@freebsd.org Subject: Re: Exim Socket Bind Problem Message-ID: <86f771$2s5f$1@twwells.com> References: Date: Sun, 23 Jan 2000 10:38:00 -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Michael Bartlett 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. -- Bill Wells bill@twwells.com I'm looking for work: Unix/C since 83, Internet since 89, FreeBSD from its beginning, Web/CGI/Perl/HTML since 96. Programmer, project leader, system admin, network admin. Contract/hire. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message