Date: Wed, 5 Jan 2000 23:22:12 -0600 From: Ade Lovett <ade@lovett.com> To: Adam <bsdx@looksharp.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Strange UDP messages Message-ID: <20000105232212.C49125@lovett.com> In-Reply-To: <Pine.BSF.4.21.0001052141540.17839-100000@turtle.looksharp.net>; from bsdx@looksharp.net on Wed, Jan 05, 2000 at 09:43:47PM -0500 References: <20000106122321.P30038@freebie.lemis.com> <Pine.BSF.4.21.0001052141540.17839-100000@turtle.looksharp.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 05, 2000 at 09:43:47PM -0500, Adam wrote: > > > >> And why didn't it happen before the machine mysteriously rebooted > >> itself this morning? (This is 3.3-RELEASE with comsat disabled in > >> /etc/inetd.conf) > > > >Well, that's the reason. Disable comsat, and you won't be able to > >connect. > > I get these too and since I have comsat disabled I'd like to stop whatever > it is from trying to notifying comsat :) Pretty annoying.. It's almost certainly going to be procmail.. by default, the sources (including from the port) will build with the code that tries to talk to comsat on local mail delivery. Rebuilding with -DNO_COMSAT added to the CFLAGS fixes that (sadly, there doesn't appear to be a run-time flag to set this, perhaps there needs to be). -aDe > [snipped named stuff] -- Ade Lovett, Austin, TX. 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?20000105232212.C49125>