This report was from a customer.
Basically, syslog fails to log packets that match logging rules under
certain circumstances. He has about 200 packet filtering rules, and has
to restart the logger in order for logging to work. I was not able to
duplicate the problem with a single rule.
He also pointed me to a patch against sysklogd that reportedly fixes the
Um, the 'patch-sysklogd-1-3-31-ksymoops-1.gz' that's in
that directory shouldn't have *anything* to do with
whether or not ipchains-type packets are logged.
Actually, does he have klogd running?
One of the things that patch fixes is a possible
segfault in klogd - if klogd died, ipchains-type
packets wouldn't be logged.
In any case, the segfault fixed by that patch
is fixed in the latest sysklogd in Raw Hide.