new kernel (surely r318877 and later) and old syslog in a jail = NOK.

I remember some mails about syslog going 100% COU some weeks ago, but thought it was solved. As we have the goal to keep backward compatibility, what is the issue here? I have this in the kernel:
options         COMPAT_FREEBSD32
options         COMPAT_FREEBSD10
options         COMPAT_FREEBSD11

new kernel and new syslog = OK

http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    netch...@freebsd.org  : PGP 0x8F31830F9F2772BF

Attachment: pgpoa2pSQdNGR.pgp
Description: Digitale PGP-Signatur

Reply via email to