Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Customize log message routing with syslog.conf' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Customize log message routing with syslog.conf
Authored by: 47ronin on Mar 10, '04 04:41:20PM

My IPFW hits are still in system.log and my ipfw.log is at 0. I even HUP'd syslogd. Any idea why?



[ Reply to This | # ]
Customize log message routing with syslog.conf
Authored by: jbc on Mar 10, '04 10:50:53PM

Adding the ipfw.log redirect worked for me first try. Except I think I rebooted the system after modifying syslog.conf. Don't know if this makes a difference.

Are you running 10.3.2? One thing I always wonder about these oddball things that Apple didn't document is whether they've been in OS X since 10.0 or whether they were silently added to some later revision. Found a reference to the syslog.conf block syntax on the Hints Forums in a post from 2002, but there's no mention of whether it actually worked or not.



[ Reply to This | # ]
syslog.conf doesn't solve everything!!!
Authored by: lennyb on Jan 06, '06 06:16:06PM

I don't wanna log in vain for your love. I was practically suicidal trying to stop this constant ipfw logging until I found the secret. Drop these lines in /etc/sysctl.conf for permanant changes after a reboot:

net.inet.tcp.log_in_vain: 1
net.inet.udp.log_in_vain: 1

you can make the constant logging stop RIGHT NOW interactively by typing (as root):

sysctl -w net.inet.tcp.log_in_vain=0
sysctl -w net.inet.udp.log_in_vain=0

open up your Apple Console.app and toggle these two values back and forth to see that I'm correct.



[ Reply to This | # ]