summaryrefslogtreecommitdiff
path: root/man/NetworkManager.xml
Commit message (Collapse)AuthorAgeFilesLines
* all: say Wi-Fi instead of "wifi" or "WiFi"Lubomir Rintel2018-11-291-1/+1
| | | | | | | | 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.
* man: clarify udev property "NM_UNMANAGED" in `man NetworkManager`Thomas Haller2018-10-261-10/+7
|
* man/NetworkManager: document --configure-and-quit optionlr/initrdLubomir Rintel2018-09-181-0/+7
|
* dispatcher: add NM_DISPATCHER_ACTION environment variableThomas Haller2018-06-181-0/+7
| | | | | | | | | | | | | | | | | | | | Previously, the action was only passed as the first command line argument to the dispatcher scripts. Now, also set it via the "$NM_DISPATCHER_ACTION" environment variable. The main purpose is to have a particular, nm-dispatcher specific variable that is always set inside the dispatcher scripts. For example, imagine you have a script that can be either called by dispatcher or some other means (manually, or spawned via /etc/NetworkManager/dispatcher.d/11-dhclient). Then it might make sense to differenciate from inside the script whether you are called by nm-dispatcher. But previously, there was no specific environment variable that was always set inside the dispatcher event. For example, with the "hostname" action there are no other environment variables. Now (with version 1.12), you can check for `test -n "$NM_DISPATCHER_ACTION"`. (cherry picked from commit ce9619047c5daac9a006d16d07453d50e0520e71)
* man: document all setting plugins in NetworkManager.conf manualThomas Haller2017-12-211-3/+3
| | | | although they are deprecated and unused, document them.
* man: use <filename> to mark file namesLubomir Rintel2016-11-111-12/+16
| | | | | This gives the templates a chance to do something extra clever with the formatting. The templates, of course, choose not to :(
* man: link to some online resourcesLubomir Rintel2016-11-111-0/+9
|
* man: get rid of the extra capitalization in docbook sourceLubomir Rintel2016-11-111-2/+2
| | | | The temaplates capitalize the names if they wish.
* man: Added documentation for the connectivity-change dispatcher hookMario Sanchez Prada2016-07-281-1/+17
| | | | | | | Also added documentation for the new CONNECTIVITY_STATE environment variable, that will also be avaiblable in those hooks. https://bugzilla.gnome.org/show_bug.cgi?id=768969
* man: turn the manual page cross-references into linksLubomir Rintel2016-06-211-8/+8
| | | | | | | | This improves the HTML rendering. But it also causes a lot of non-resolvable linkends warning when rendering a separate manual pages into roff/mman. The messages are harmless, but still a bit ugly.
* config,dns: support Reload flags to specify that only parts should be reloadedThomas Haller2016-06-011-0/+5
| | | | | | | | | | Support 3 new flags for Reload: - 0x01 (CONF): reload the configuration from disk - 0x02 (DNS_RC): write DNS configuration to resolv.conf - 0x04 (DNS_FULL): restart DNS plugin Omitting all flags is the same as reloading everything, thus SIGHUP.
* man: update documenting signals in NetworkManager manualThomas Haller2016-06-011-4/+20
|
* man: add missing comma in NetworkManager.xml 'see also' sectionBeniamino Galvani2016-04-161-1/+1
|
* man: clarify the license of the manualslr/manLubomir Rintel2016-04-081-3/+16
| | | | It's included from GFDL 1.1+ document; it should be GFDL too.
* man: move nmcli-examples to section 7Lubomir Rintel2016-04-051-1/+1
| | | | It really is not a configuration file and doesn't belong to section 5.
* man: include version from a XML entityLubomir Rintel2016-04-051-3/+6
| | | | | | | | This way it's consistently used across all manual page without a need for XSL templating. Also, the entities file could in future possibly be used to template the build-time configurables such as filesystem paths or bug tracker URL.
* man: update version number and dates in manual pagesBeniamino Galvani2016-03-091-1/+1
| | | | | | | Bump NM version number to 1.2 and add the project name to non-XML pages. Also, update the dates to the date of the last non-trivial change and update their format to YYYY-MM-DD, as specified by 'man man-pages'.
* man: clarify DEVICE_IFACE vs. DEVICE_IP_IFACE in `man NetworkManager`Thomas Haller2016-02-221-2/+7
|
* man: replace tabs by eight spaces in xml manual pagesThomas Haller2016-01-271-67/+67
|
* man: document the effects of supported signalsBeniamino Galvani2016-01-191-0/+31
|
* man: fix typosBeniamino Galvani2015-12-241-2/+2
|
* main: add argument --print-config to NetworkManagerThomas Haller2015-11-221-0/+6
|
* nm-dispatcher: allow scripts to be marked as no-waitBeniamino Galvani2015-08-251-4/+6
| | | | | | | | When a script is a symbolic link to the 'no-wait.d' subdirectory, the dispatcher now schedules it immediately and in parallel with other no-wait scripts. https://bugzilla.gnome.org/show_bug.cgi?id=746703
* man: clearify the meaning of the interface argument for dispatcher scriptsThomas Haller2015-08-191-1/+4
|
* platform: give the platform an opportunity to override default-unmanagedLubomir Rintel2015-03-231-0/+28
| | | | | | | | | | | | | | | | | | | | Some out of tree drivers add Ethernet devices that are supposed to be managed by other their tooling, e.g. VirtualBox or VMWare. Rather than hardcoding their drivers (at least VirtualBox doesn't even set a "driver" property in sysfs) or hardcoding a logic that identifies such devices let's just add a possibility to blacklist them in udev. This makes it possible for whoever who ships such a driver to ship rules that prevent NetworkManager from managing the device itself. Furthermore it makes it possible for the user with special needs leverage the flexibility of udev rules to override the defaults. In the end the user can decide to let NetworkManager manage default-unmanaged interfaces such as VEth or turn on default-unmanaged for devices on a particular bus. An udev rule for VirtualBox would look like this: SUBSYSTEM=="net", ENV{INTERFACE}=="vboxnet[0-9]*", ENV{NM_UNMANAGED}="1"
* dispatcher: add an env var indicating a connection is "external"Dan Winship2015-01-191-0/+7
| | | | | | Add CONNECTION_EXTERNAL=1 to the environment when dispatching actions on a "generated-assumed" connection (ie, one that was created outside of NM).
* dispatcher: expose connection D-Bus pathDan Winship2015-01-191-0/+6
| | | | | | | | | | | src/nm-dispatcher.c was passing the connection's D-Bus path to the dispatcher, which was then ignoring it. Meanwhile, test-dispatcher-envp was passing a fake D-Bus path with the wrong name (which didn't actually matter since nm_dispatcher_utils_construct_envp() ignored it anyway). Fix it so that the path gets exposed as CONNECTION_DBUS_PATH, and adjust the tests for that.
* dispatcher: pass CONNECTION_FILENAME to dispatcher scriptsDan Winship2015-01-121-0/+6
|
* man: fix formatting leftover from man -> xml migrationJiří Klimeš2014-11-191-3/+3
|
* man: update version reference to 1.0 in manual pagesJiří Klimeš2014-11-191-4/+4
|
* dispatcher: introduce new env variables for gateway address (bgo #740363)Jiří Klimeš2014-11-191-1/+8
| | | | | | | | | | | IP4_GATEWAY VPN_IP4_GATEWAY IP6_GATEWAY VPN_IP6_GATEWAY We still put gateway into IP[46]_ADDRESS_N for backward compatibility. https://bugzilla.gnome.org/show_bug.cgi?id=740363
* dispatcher: use separate directories for pre-up/pre-down eventsDan Williams2014-06-061-3/+46
| | | | | | To ensure that NetworkManager does not block needlessly for events which have no scripts, require scripts that respond to blocking events to opt into the action.
* man: updates to the dispatcher sectionDan Winship2014-04-181-0/+9
| | | | | | | | Mention that the dispatcher kills slow scripts (https://bugzilla.redhat.com/show_bug.cgi?id=982734) and that it runs all scripts that have been queued, even if later events make that "wrong". (Mentioned in https://bugzilla.gnome.org/show_bug.cgi?id=721971, although that bug proposes changing this behavior, not documenting it.)
* man: update dispatcher scripts description in NetworkManager(8) manual pageJiří Klimeš2014-01-271-47/+124
|
* logging: allow per-domain log level overridesDan Winship2013-12-201-4/+9
| | | | | Allow specifying log domains like "DEFAULT,WIFI:DEBUG" to override the log level on a per-domain basis.
* man: add 'nmcli-examples' manual page with examples of nmcli usageJiří Klimeš2013-07-221-0/+1
| | | | (and add a reference to 'nmcli-examples' to other man pages)
* core: add single-letter command-line flagsDan Winship2013-05-211-5/+5
| | | | | | | | Add single-letter options for --version, --no-daemon, --debug, and --pid-file (and document them, as well as the existing single-letter option for --help). https://bugzilla.gnome.org/show_bug.cgi?id=700550
* main: add --debug, fix logging under systemdDan Winship2013-05-211-3/+7
| | | | | | | | | | | | | | | When run with --no-daemon, NM used to duplicate all syslog output to stderr, for ease of debugging. But this meant it had to tell systemd to ignore stderr, so you wouldn't get duplicated log entries. But that meant we lost error messages that didn't go through nm_log. (eg, g_warning()s and g_return_if_fail()s). Fix this by making --no-daemon no longer duplicate syslog output to stderr, and removing the "StandardError=null" from the systemd service file. To get the old behavior, you can use --debug instead of --no-daemon. https://bugzilla.gnome.org/show_bug.cgi?id=700550
* man: add a few pieces of metadata to silence DocBook warnings in manpagesJiří Klimeš2013-05-071-4/+7
| | | | and correct "SEE ALSO"
* man: rewrite NetworkManager.8 and NetworkManager.conf.5 in DocBookColin Walters2013-04-241-0/+223
DocBook is not my favorite thing in the world, but it's <lots-of-emphasis>far</lots-of-emphasis> saner than troff. Some style parts cribbed from systemd. This is preparatory work for actually improving the content of the man pages.
View Lorry Controller Status