no explanation for the events in the networkd-dispatcher manpage
Bug #1787495 reported by
Steve Langasek
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| networkd-dispatcher (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Bionic |
In Progress
|
Undecided
|
Unassigned | ||
| Cosmic |
In Progress
|
Undecided
|
Unassigned | ||
| systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Bionic |
Triaged
|
Undecided
|
Unassigned | ||
| Cosmic |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
[Impact]
networkd-dispatcher supports four hook directories:
$ ls /usr/lib/
dormant.d no-carrier.d off.d routable.d
$
The manpage does not define what these hooks mean. 'routable' and 'no-carrier' are self-explanatory, but it's not at all clear what 'dormant' vs 'off' mean. It's not at all clear what events one should expect to see as part of device bring-up.
This needs to be better documented.
[Test case]
Check that it networkd-
[Regression potential]
If user updates networkd-dispatcher before systemd, they get the reference to networkctl(1) in networkd-
| tags: | added: id-5b76028cae42945920e85c44 |
Revision history for this message
| Julian Andres Klode (juliank) wrote | #1 |
Revision history for this message
| Julian Andres Klode (juliank) wrote | #2 |
| Changed in networkd-dispatcher (Ubuntu): | |
| status: | New → In Progress |
Revision history for this message
| Julian Andres Klode (juliank) wrote | #3 |
Revision history for this message
| Julian Andres Klode (juliank) wrote | #4 |
Revision history for this message
| Julian Andres Klode (juliank) wrote | #5 |
| Changed in systemd (Ubuntu): | |
| status: | New → In Progress |
Revision history for this message
| Julian Andres Klode (juliank) wrote | #6 |
| Changed in systemd (Ubuntu): | |
| status: | In Progress → Fix Released |
| Changed in networkd-dispatcher (Ubuntu): | |
| status: | In Progress → Fix Committed |
| Changed in systemd (Ubuntu Cosmic): | |
| status: | New → Fix Released |
| Changed in networkd-dispatcher (Ubuntu Cosmic): | |
| status: | New → In Progress |
| Changed in networkd-dispatcher (Ubuntu Bionic): | |
| status: | New → In Progress |
| Changed in systemd (Ubuntu Bionic): | |
| status: | New → Triaged |
| description: | updated |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #7 |
| Changed in networkd-dispatcher (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
From systemd:
/* Get operational state from ifindex.
* Possible states:
* off: the device is powered down
* no-carrier: the device is powered up, but it does not yet have a carrier
* dormant: the device has a carrier, but is not yet ready for normal traffic
* carrier: the link has a carrier
* degraded: the link has carrier and addresses valid on the local link configured
* routable: the link has carrier and routable address configured
We don't have dirs for degraded and carrier. Not sure if they get exposed or not.
I'm not sure if they shouldn't be documented in systemd somewhere, though.