From owner-freebsd-questions Thu Jan 6 4:41:56 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mailgw01.execpc.com (mailgw01.execpc.com [169.207.2.78]) by hub.freebsd.org (Postfix) with ESMTP id 05E19155A5 for ; Thu, 6 Jan 2000 04:41:54 -0800 (PST) (envelope-from hamilton@pobox.com) Received: from woodstock.monkey.net (planetx-1-5.mdm.mkt.execpc.com [169.207.119.5]) by mailgw01.execpc.com (8.9.1) id GAA16283 for ; Thu, 6 Jan 2000 06:41:42 -0600 Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id DAE72193 for ; Thu, 6 Jan 2000 06:44:07 -0600 (CST) X-Mailer: exmh version 2.1.1 10/16/1999 To: freebsd-questions@FreeBSD.ORG Subject: Re: Strange UDP messages In-reply-to: Your message of "Thu, 06 Jan 2000 00:30:02 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 06:44:07 -0600 From: Jon Hamilton Message-Id: <20000106124407.DAE72193@woodstock.monkey.net> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Ada m wrote: } >> 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). Sure there is. From procmailrc(1): COMSAT Comsat(8)/biff(1) notification is on by default, it can be turned off by setting this variable to `no'. Alternatively the biff-ser- vice can be customised by setting it to either `service@', `@hostname', or `service@host- name'. When not specified it defaults to biff@localhost. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message