delta/NetworkManager.git/man/NetworkManager.xml, branch lr/asserts gitlab.freedesktop.org: NetworkManager/NetworkManager.git man: add NetworkManager-wait-online.service.8 manual 2022-03-02T15:09:16+00:00 Thomas Haller thaller@redhat.com 2022-03-02T10:05:45+00:00 df94cb2116234786d00a5d7149d796ed8a502cc2 NetworkManager-wait-online is a constant source of confusion, as it seems to delay the boot (when it's often just the messenger or either a network problem, a NetworkManager misconfiguration or a misconfiguration of other systemd services). Try to clear that up with a manual page. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1130 
NetworkManager-wait-online is a constant source of confusion,
as it seems to delay the boot (when it's often just the messenger
or either a network problem, a NetworkManager misconfiguration
or a misconfiguration of other systemd services).

Try to clear that up with a manual page.

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1130
man: update URL for networkmanager.dev home page 2021-08-03T12:57:35+00:00 Thomas Haller thaller@redhat.com 2021-08-03T12:57:35+00:00 7a39f1f7e7ee6d3d409523957e889bd8a940d414 






core: force emission of DNS_CONFIG_CHANGED signal on SIGUSR1
2021-05-03T20:13:36+00:00

Beniamino Galvani
bgalvani@redhat.com

2021-04-29T08:40:27+00:00

fa1f628bce9f82bd4c753d75709203c72fff310c

If the configuration contains dns=none and resolv.conf is updated
through a dispatcher script, currently there is no way to tell NM that
the content of resolv.conf changed, so that it can restart a hostname
resolution.

Use SIGUSR1 (and SIGHUP) for that.





If the configuration contains dns=none and resolv.conf is updated
through a dispatcher script, currently there is no way to tell NM that
the content of resolv.conf changed, so that it can restart a hostname
resolution.

Use SIGUSR1 (and SIGHUP) for that.







man: split NetworkManager-dispatcher(8) manual page out of NetworkManager(8)
2021-03-16T16:01:53+00:00

Thomas Haller
thaller@redhat.com

2021-03-16T13:30:58+00:00

9c0c0ac966cb4dddaeba72580edc20c777280858

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/784





https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/784







man: expand DEBUGGING section in `man NetworkManager`
2020-09-02T14:45:14+00:00

Thomas Haller
thaller@redhat.com

2020-09-02T14:41:46+00:00

9c732c12bdfe83731a889a4d3acc65b95d7ca89c












man: update bug tracker in `man NetworkManager`
2020-09-02T13:56:10+00:00

Thomas Haller
thaller@redhat.com

2020-09-02T13:56:10+00:00

ab8b148d41b677530f6cc96d6948291457011ebe












man: fix description of v2 secret key in `man NetworkManager`
2020-09-02T12:52:46+00:00

Thomas Haller
thaller@redhat.com

2020-09-02T11:20:09+00:00

40185042472163550054eb9f3011f92fc6464689

Fixes: 0aa09da5f46d ('man: explain "/var/lib/NetworkManager/secret-key" in `man NetworkManager`')





Fixes: 0aa09da5f46d ('man: explain "/var/lib/NetworkManager/secret-key" in `man NetworkManager`')







man: explain "/var/lib/NetworkManager/secret-key" in `man NetworkManager`
2020-09-02T10:10:04+00:00

Thomas Haller
thaller@redhat.com

2020-09-02T09:55:02+00:00

0aa09da5f46dc79af9ce99751f71940c6c4736da












dispatcher: clarify documentation about first argument to dispatcher scripts for "connectivity-change"
2020-04-30T19:53:21+00:00

Thomas Haller
thaller@redhat.com

2020-04-29T07:47:06+00:00

62b135d33799a26a0a06aa713708095b0b55a85b

The manual page claimed that for "connectivitiy-change" actions, the dispatcher
scripts would get as first argument (the device name) "none". That was not done,
only for "hostname" actions.

For consistency, maybe that should be adjusted to also pass "none" for connectivity
change events. However, "none" is really an odd value, if there is no device. Passing
an empty word is IMO nicer. So stick to that behavior, despite being inconsistent.
Also fix the documentation about that.

(cherry picked from commit 0b168f7b995e0eac681a985e69f0f036c8db15c4)





The manual page claimed that for "connectivitiy-change" actions, the dispatcher
scripts would get as first argument (the device name) "none". That was not done,
only for "hostname" actions.

For consistency, maybe that should be adjusted to also pass "none" for connectivity
change events. However, "none" is really an odd value, if there is no device. Passing
an empty word is IMO nicer. So stick to that behavior, despite being inconsistent.
Also fix the documentation about that.

(cherry picked from commit 0b168f7b995e0eac681a985e69f0f036c8db15c4)







all: say Wi-Fi instead of "wifi" or "WiFi"
2018-11-29T16:53:35+00:00

Lubomir Rintel
lkundrak@v3.sk

2018-11-21T10:32:38+00:00

b385ad015944af4349b56ffe38ab6369f78655b9

Correct the spelling across the *entire* tree, including translations,
comments, etc. It's easier that way.

Even the places where it's not exposed to the user, such as tests, so
that we learn how is it spelled correctly.





Correct the spelling across the *entire* tree, including translations,
comments, etc. It's easier that way.

Even the places where it's not exposed to the user, such as tests, so
that we learn how is it spelled correctly.