Date: Wed, 01 Jan 2020 04:22:09 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 70335] inetd(8) inconsistent syslog behavior when max children configured in inetd.conf Message-ID: <bug-70335-227-Y99I80M58M@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-70335-227@https.bugs.freebsd.org/bugzilla/> References: <bug-70335-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D70335 --- Comment #2 from commit-hook@freebsd.org --- A commit references this bug: Author: kevans Date: Wed Jan 1 04:22:05 UTC 2020 New revision: 356247 URL: https://svnweb.freebsd.org/changeset/base/356247 Log: inetd: track all child pids, regardless of maxchild spec Currently, child pids are only tracked if maxchildren is specified. As a consequence, without a maxchild limit we do not get a notice in syslog on children aborting abnormally. This turns out to be a great debugging aide= at times. Children are now tracked in a LIST; the management interface is decidedly less painful when there's no upper bound on the number of entries we may have at the cost of one small allocation per connection. PR: 70335 Changes: head/usr.sbin/inetd/inetd.c head/usr.sbin/inetd/inetd.h --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-70335-227-Y99I80M58M>