Page MenuHomeFreeBSD

Fix and document kern.signal.coredump devctl
ClosedPublic

Authored by trasz on Jul 18 2018, 4:32 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jun 21, 3:57 PM
Unknown Object (File)
Fri, Jun 21, 10:42 AM
Unknown Object (File)
Fri, Jun 21, 5:49 AM
Unknown Object (File)
Dec 4 2023, 9:59 AM
Unknown Object (File)
Oct 4 2023, 10:22 AM
Unknown Object (File)
Sep 10 2023, 10:47 AM
Unknown Object (File)
Aug 28 2023, 5:24 AM
Unknown Object (File)
Aug 13 2023, 12:18 PM
Subscribers

Details

Summary

Rename the kernel.signal.coredump devctl notification
to kern.signal.coredump and document it in devd.conf(5).

At this point we invoke both kernel.signal.coredump
and kern.signal.coredump, for backwards compatibility.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

You did not provided a single reason for the renaming.

Without renaming we would have both "kern" and "kernel". In devd.conf(5) man page we already have the "kern" top-level, described as "Events related to the kernel"; leaving the old name would require adding a new top level "kernel" - described as "Also events related to the kernel", I guess?

Without renaming we would have both "kern" and "kernel". In devd.conf(5) man page we already have the "kern" top-level, described as "Events related to the kernel"; leaving the old name would require adding a new top level "kernel" - described as "Also events related to the kernel", I guess?

Yes, the event should be not renamed. It is unfortunate that we have this inconsistency, but I do not see a documentation issue strong enough to warrant the a) the breakage of the interface or b) doubling of the events sent on the core dump.

This revision was not accepted when it landed; it landed in state Needs Review.Jul 20 2018, 2:32 PM
This revision was automatically updated to reflect the committed changes.