#
1a2a0db0 |
| 15-Dec-2024 |
Kyle Evans <kevans@FreeBSD.org> |
tests: kern: improve logsigexit test
Use dmesg(8) instead rather than relying on a particular syslogd configuration, and just skip the test if we can't access the msgbuf.
While we're here, remove s
tests: kern: improve logsigexit test
Use dmesg(8) instead rather than relying on a particular syslogd configuration, and just skip the test if we can't access the msgbuf.
While we're here, remove some debugging output that we don't actually need.
show more ...
|
#
9647bf24 |
| 14-Dec-2024 |
Kyle Evans <kevans@FreeBSD.org> |
tests: kern: add some tests for recently added logsigexit
We don't bother tweaking the sysctl in these tests, we'll just try with it forced both on and off via proccontrol(1). This could be problem
tests: kern: add some tests for recently added logsigexit
We don't bother tweaking the sysctl in these tests, we'll just try with it forced both on and off via proccontrol(1). This could be problematic in the face of pid wrapping if we got really unfortunate, but the potential solutions need careful consideration- you probably don't want to assume a certain velocity of messages into syslog, so just checking the last N lines is probably similarly flakey.
show more ...
|