On Wed, Feb 21, 2001 at 06:20:13PM +0900, Hajimu UMEMOTO wrote: > lists> Thanks, yes, that works...but, ugh. So some backward-compatibility was broken > lists> in 4.2-STABLE...and that should probably be fixed... > > It is security reason. The -s option is specified by default under > 4.X or later. If you need, you can still enable insecure mode by > omitting -s from syslogd_flags in /etc/rc.conf. However, if you > intend to log within the host, it is not recommended. > Please refer manpage of syslogd. uh, nope, it failed even on a 4.2-STABLE machine (which I use as a loghost for the local network) that has syslogd running as: 37894 ?? Ss 0:03.27 syslogd -n -vv -a 10.10.10.0/24 unless I force it to use the unix domain socket as suggested above. But that gave me an idea -- I forced logger to use PF_INET by specifying the -h option, and that doesn't work -- I even tried adding -a 127.0.0.1/32 to the syslogd command line hoping that that might make a difference: 41337 ?? Ss 0:00.01 syslogd -n -vv -a 10.10.10.0/24 -a 127.0.0.1/32 but that doesn't help either. The syslog host is 10.10.10.5 and I tried both: logger -h 10.10.10.5 -p 'crit' "this is a test" logger -h 127.0.0.1 -p 'crit' "this is a test" and neither worked. However it is receiving syslog messages from other hosts without a problem where I have it specified in their syslog.conf as: *.* @10.10.10.5 (I noticed that kern.debug and possibly kern.info messages don't get relayed, but that is another thread and I almost understand why that is but couldn't find it in the syslogd code) There is something screwy about the PF_INET stuff which neither logger nor Sys::Syslog like...and this is broken in regards to previous behaviour. Thanks, Adi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
