From owner-freebsd-stable Wed Feb 21 11:58:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id 5578337B65D for ; Wed, 21 Feb 2001 11:58:30 -0800 (PST) (envelope-from ume@mahoroba.org) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.2+3.4W/3.7W-light) with UUCP id f1LJwKx07155; Thu, 22 Feb 2001 04:58:20 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from peace.mahoroba.org (IDENT:q4buTTQCJGsUyYE2TnippEhIEAU/YXOBePMjZ+DOiXMpaMP2ff9/QkkTufbt9AQv@peace.mahoroba.org [3ffe:505:2:0:200:f8ff:fe05:3eae]) by mail.mahoroba.org (8.11.2/8.11.2/chaos) with ESMTP/inet6 id f1LJtsB08717; Thu, 22 Feb 2001 04:55:55 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Thu, 22 Feb 2001 04:55:54 +0900 (JST) Message-Id: <20010222.045554.71152050.ume@mahoroba.org> To: lists@lists.grot.org Cc: freebsd-stable@freebsd.org Subject: Re: syslog changes in 4.2-stable? From: Hajimu UMEMOTO In-Reply-To: <20010221105905.A41009@mighty.grot.org> References: <20010220225849.A37315@mighty.grot.org> <20010221.182013.39234185.ume@imasy.or.jp> <20010221105905.A41009@mighty.grot.org> X-Mailer: xcite1.38> Mew version 1.95b97 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, >>>>> On Wed, 21 Feb 2001 10:59:05 -0800 >>>>> lists said: lists> uh, nope, it failed even on a 4.2-STABLE machine (which I use as a loghost for lists> the local network) that has syslogd running as: lists> 37894 ?? Ss 0:03.27 syslogd -n -vv -a 10.10.10.0/24 lists> unless I force it to use the unix domain socket as suggested above. lists> But that gave me an idea -- I forced logger to use PF_INET by specifying the lists> -h option, and that doesn't work -- I even tried adding -a 127.0.0.1/32 to the lists> syslogd command line hoping that that might make a difference: lists> 41337 ?? Ss 0:00.01 syslogd -n -vv -a 10.10.10.0/24 -a 127.0.0.1/32 lists> but that doesn't help either. The syslog host is 10.10.10.5 and I tried both: lists> logger -h 10.10.10.5 -p 'crit' "this is a test" lists> logger -h 127.0.0.1 -p 'crit' "this is a test" I just tried on my box and it runs. If you don't specify service at -a option, 514 is assumed by default. It's a privilege port and general users cannot bind it. If you wish to allow the connections from general user, you must specify * as service like follows: syslogd -n -vv -a '10.10.10.0/24:*' -a '127.0.0.1/32:*' lists> and neither worked. However it is receiving syslog messages from other hosts lists> without a problem where I have it specified in their syslog.conf as: lists> *.* @10.10.10.5 Since syslogd does bind to 514, it works. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message