:
: So I started thinking that maybe the problem was actually in
:syslog (or amd's interface to it). So I disabled the following two options
:in my amd.conf file:
:
:log_file = syslog:local7
:log_options = all
:
: And lo and behold, it worked like a charm. I was able to run my
:conf-building script for my web server 20 times in a row with no ill
:effects. Previously the best I could do was 3 times before it hung.
:
: After confirming that it worked with no logging, I tried enabling
:logging to a regular file, and that also worked like a charm. After
:turning syslog style logging back on, it locked up cold, with a very
:similar traceback.
:
: If anyone wants to work on this, let me know.
:
:Doug
Are you syslogging to the console by any chance? Try messing around
with /etc/syslog.conf and see if just plain file logging prevents the
lockup -- you could even try turning off all logging (but leaving syslog
running, i.e. turning it into a sink-null) to see if that has an effect.
-Matt
Matthew Dillon
<dil...@backplane.com>
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
