https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279203
Bug ID: 279203
Summary: logger: Forking many logger executables at once
renders machine unresponsive
Product: Base System
Version: 13.3-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: bin
Assignee: b...@freebsd.org
Reporter: gre...@freebsd.org
CC: r...@freebsd.org
Forking logger many times like this:
#!/bin/sh
for id in $(jot 100); do
logger -p local2.info -t pot "wledkjweldjwldjkwedj" &
done
sends the machine into some race condition, causing loads of 300-500. I can
reproduce it on multicore machines (including within bhyve), not on single
core. Load is mostly caused by system calls. When knowing pids, it's sometimes
possible to recover the host by killing all logger processes (killall won't
work though, as the machine is too loaded for that).
I could not reproduce this on 13.2 (at least not as easily). When building
logger without capsicum, this doesn't happen, but that could be a red herring.
Happens on 13.3 as well as 13.3p2.
This is causing quite some headache. We put logger under a lock to reduce
concurrency, which made things better, but we still see the general situation
(either other things call logger or, more likely, this is just a symptom of a
bigger underlying issue).
--
You are receiving this mail because:
You are the assignee for the bug.
