in preparing other changes (port in forward actions, etcetera) for
IU-syslogd, I have discovered that the handling at reload of
configuration, as well as failed implementation of the action
fields, will lead do memory leaks over time.
It shouldn't leak of course.
Using the following setup
#!/bin/sh
LOGDCONF=/tmp/logd.conf
cat > $LOGDCONF <<STOP
*.* @localhost
*.* |/dev/null
*.* /tmp/bucket
*.* blind,mice,and,cats
STOP
sudo ./src/syslogd -d --pidfile=/tmp/syslogd.pid -f$LOGDCONF --no-klog
-p/tmp/log $*
## End of script
I have sent USR1 once and HUP twenty times to the process without
detecting a crash or other malfunction.
What do you mean with a crash? Did it crash before?
