Date: Sat, 06 Apr 2024 12:15:29 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 278195] daemon is exiting without informing that it failed to execute Message-ID: <bug-278195-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278195 Bug ID: 278195 Summary: daemon is exiting without informing that it failed to execute Product: Base System Version: 13.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: skenizen@gmail.com When launching a daemon in the jail (as a specified user) /usr/sbin/daemon = was exiting with return code 0 and not outputting anything in the syslogs. This happened on a jail I've erroneously upgraded from FreeBSD 13.2-RELEASE= to FreeBSD 13.3-RELEASE on a system host with 13.2-RELEASE. I've seen other users mentioning similar issues on TrueNAS forums pinpointi= ng to kqueuex() being the culprit for ABI incompatibility (https://www.truenas.com/community/threads/warning-dont-upgrade-your-truena= s-core-jails-to-freebsd-13-3-just-yet.117018). Although my bug report is not about this, but more about the lack of information on the user that something wrong happened. I'd expect at minimu= m a different return code than 0 (and preferably an explicit error in the log t= oo). --=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-278195-227>