summaryrefslogtreecommitdiff
path: root/data
Commit message (Collapse)AuthorAgeFilesLines
* Split out the bits which determine ID_NET_DRIVER or DRIVERS into separate ↵Michael Biebl2015-08-313-7/+15
| | | | | | | | | udev rules file Those are not required with systemd-udevd v210 or newer. This way distros which have a new enough version of udev can skip installing 84-nm-drivers.rules. While at it, don't use absolute paths for sed and ethtool.
* udev-rules: avoid ifname shell expansionLubomir Rintel2015-08-191-1/+1
|
* udev-rules: one less useless use of catLubomir Rintel2015-08-181-2/+2
|
* udev-rules: only invoke ethtool for existing interfacesBeniamino Galvani2015-08-181-0/+1
| | | | | ethtool may cause the auto-loading of a kernel module for non-existing interface-names. Avoid that by checking whether such an interface exists.
* Revert "udev-rules: only invoke ethtool for existing interfaces"Lubomir Rintel2015-08-181-1/+1
| | | | | | | This reverts commit 44fee0f6fff42773aa73a9a46220db697907751f. Bad quoting here. Also, this is not quite the best fix for the issue, filtering on ACTION=="add" is probably a bit more elegant.
* udev-rules: only invoke ethtool for existing interfacesBeniamino Galvani2015-08-111-1/+1
| | | | | | | ethtool may cause the auto-loading of a kernel module for non-existing interface-names. Avoid that by checking whether such an interface exists. This is inherently racy.
* systemd: require CAP_AUDIT_WRITE for NetworkManager serviceBeniamino Galvani2015-08-041-1/+1
| | | | We need it to write messages to kernel auditing log.
* service: harden the NetworkManager service a bitlr/systemd-hardenedLubomir Rintel2015-07-011-0/+3
| | | | | | Tested with dnsmasq (ipv4.method=shared), openvpn & vpnc. https://bugzilla.gnome.org/show_bug.cgi?id=750598
* platform: don't use udev for link type determinationDan Williams2015-05-012-9/+1
| | | | | This allows us to always announce links when the kernel advertises them, instead of waiting for udev.
* systemd: make NetworkManager reloadable via SIGHUPThomas Haller2015-04-171-0/+1
| | | | | | | | | | | | | Since f9e4af2, parts of the configuration can be reloaded by sending SIGHUP to NetworkManager. Add ExecReload option to service file to support reloading by sending a signal. Note that 'man 5 systemd.service' advices to use a blocking command instead of a sending a signal. Later we should add a D-Bus method to allow reloading synchronously. For now, this is better then nothing. https://mail.gnome.org/archives/networkmanager-list/2015-April/msg00042.html
* data: move OLPC MESH udev rules away from calloutsLubomir Rintel2015-03-232-1/+10
| | | | | | | No idea why was it there in the first place. This also fixes a bug that the rules file was conditionally included in dist depending on presence of udev dir at configure time.
* data: add udev rules to make emulated ethernet devices default unmanagedLubomir Rintel2015-03-232-0/+40
| | | | | | | | | There are some out-of-tree drivers that create devices masquerading as ethernets which are supposed to use their own management tools. Avoid touching them. The rules should be run after 80-net-setup-link.rules, so that the ID_NET_DRIVER is set.
* core: tell systemd to restart NetworkManager.service if it exited with ↵Mikko Rapeli2014-12-161-0/+1
| | | | | | | | | | failure (bgo #741587) Crashed NetworkManager.service was not restarted by systemd. Signed-off-by: Mikko Rapeli <mikko.rapeli@iki.fi> https://bugzilla.gnome.org/show_bug.cgi?id=741587
* dispatcher: rename executable to 'nm-dispatcher'Dan Williams2014-06-061-1/+1
|
* build: fix installing network-online.target for existing linkThomas Haller2014-06-021-1/+1
| | | | | | | | | | | | | | | | When reinstalling NM on the same location, it would fail with Making install in data make[1]: Entering directory `/home/data/src/NetworkManager/data' make[2]: Entering directory `/home/data/src/NetworkManager/data' install -d /opt/test/lib/systemd/system/network-online.target.wants ln -s /opt/test/lib/systemd/system/NetworkManager-wait-online.service /opt/test/lib/systemd/system/network-online.target.wants ln: failed to create symbolic link ‘/opt/test/lib/systemd/system/network-online.target.wants/NetworkManager-wait-online.service’: File exists make[2]: *** [install-exec-local] Error 1 https://bugzilla.gnome.org/show_bug.cgi?id=728965 Signed-off-by: Thomas Haller <thaller@redhat.com>
* implement systemd network-online.target properly (bgo #728965)Pavel Šimerda2014-05-301-0/+4
| | | | | | | | | | | | | | | Make network-online.target depend on NetworkManager-wait-online.service just as is done in Fedora. This makes network-online.target work with NetworkManager as described in systemd documentation. An alternative way would be to use a combination of setting Install.WantedBy to network-online.target and enabling the service by default. This alternative approach is currently used by systemd-networkd. https://bugzilla.gnome.org/show_bug.cgi?id=728965 Acked-By: Dan Williams <dcbw@redhat.com>
* dispatcher: tell systemd to not kill dispatcher childrenDan Winship2014-04-181-0/+4
| | | | | | | | You're supposed to be able to use dispatcher scripts to spawn long-running processes, but currently systemd will kill them when nm-dispatcher exits. Fix that. https://bugzilla.gnome.org/show_bug.cgi?id=725492
* systemd: update NetworkManager-wait-online.service to wait for startupJiří Klimeš2014-03-312-2/+2
|
* systemd: add "Before=network.service" on Fedora/RHEL (rh #1034983)Dan Winship2013-12-172-2/+3
| | | | | | On Fedora/RHEL, NetworkManager.service needs to be started before network.service, or else network.service may try to bring up NM's devices itself.
* systemd: fix up dispatcher unit install (rh #948433)Dan Williams2013-08-062-1/+1
| | | | | | | | | | | | | Lennart sez: "Oh, I wasn't aware it is short-lived only. In that case, drop the multi-user.target bit, and just make it create the dbus alias. [Install] Alias=dbus-org.freedesktop.nm-dispatcher.service And yeah, adding Also=NetworkManager-dispatcher.service to NetworkManager.service certainly would be a good idea."
* core: change the rules for ignore-carrierDan Winship2013-07-221-1/+1
| | | | | | | The previous ignore-carrier rules did not work well with dynamic IP (dhcp/slaac) connections. Change the rule so that only static IP connections can be activated when carrier is not present (but both static and dynamic connections will remain up when carrier is lost).
* server.conf: We're no longer a sample, reword introductionColin Walters2013-07-221-3/+4
| | | | Now we actually change configuration, explain that better.
* Merge some comments from server.conf into "man NetworkManager.conf"Colin Walters2013-07-221-35/+9
| | | | | The latter should have the full+canonical description, and the config file comments should be very brief, and link to it for more info.
* server.conf: Remove dns=none exampleColin Walters2013-07-221-12/+0
| | | | | This is covered in the manpage adequately, and we want this file to be actual options now, not just commented out ones.
* core: make monitor-connection-files be false by defaultDan Winship2013-07-221-9/+0
|
* core: add monitor-connection-files=false and ReloadConnectionsDan Winship2013-06-141-0/+9
| | | | | | | | | Add a "monitor-connection-files" config option, which can be set to "false" to disable automatic reloading of connections on file change. To go with this, add a new ReloadConnections method on o.fd.NM.Settings that can be used to manually reload connections, and add an nm-cli command to call it.
* systemd: update for network-online.target for systemd >= 200 (rh #787314)Dan Williams2013-06-034-4/+21
| | | | | | | systemd's new network-online target abstracts the "wait until networking is up" stuff, and NM-wait-online implements that functionality. Thus NM-wait-online should be ordered before (and thus be a dependency of) network-online.
* systemd: add service for dispatcher (rh #948433)Dan Williams2013-06-032-2/+21
|
* main: add --debug, fix logging under systemdDan Winship2013-05-211-4/+0
| | | | | | | | | | | | | | | 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
* build: Fix srcdir != builddirColin Walters2013-04-031-2/+8
|
* data: add a server.conf example fileDan Winship2013-04-032-0/+59
| | | | Add a server.conf example file, and install it to $(docdir)/examples.
* systemd: set KillMode=processDan Winship2013-01-041-0/+2
| | | | | | | | | | By default, when shutting NM down, systemd will kill everything in its cgroup. But this can cause problems (eg, NM thinking that dhclient crashed and then taking down an interface that it would otherwise have left up). Fix this by setting KillMode=process, which tells systemd to only kill NM itself, and let NM kill its children. https://bugzilla.redhat.com/show_bug.cgi?id=876218
* systemd: restore D-Bus service alias nameDan Williams2012-09-251-0/+1
| | | | Mistakenly removed while merging 86f14392fc94189d24c0e65dcc5b2db74ca709ae
* systemd: also install nm-wait-online on 'systemctl enable'Pavel Šimerda2012-09-251-1/+2
| | | | | Inspired by openSUSE patches. There is no need to require user/distributor manually enable nm-wait-online.
* systemd: suppress logging each message twice when run via systemd (rh #751275)Jiří Klimeš2012-02-071-0/+4
|
* systemd: fix NetworkManager-wait-online.service to wait for link up (rh #710502)Michal Schmidt2011-06-171-1/+2
| | | | | | | | | | | | Since commit 0ce4b6b4128f19177072d1bb5f5c3a87783256ba NetworkManager-wait-online.service quits immediately if there is no link yet. Fix it by removing the '-x' option. But if we do just that, NM-w-o would add a useless 30 seconds delay in the case when NM is not running at all. Solve this by adding a Requisite= dependency on NM. https://bugzilla.redhat.com/show_bug.cgi?id=710502
* systemd: tweak NM-wait-online.serviceBill Nottingham2011-05-101-3/+3
| | | | | | | | | | 1) Don't require NM, but run after it. This allows this service to be installed without bringing up NetworkManager. Add -x so that it exits if NM isn't running. 2) Install as a want of network.target, instead of multi-user.target. This allows us to skip it if nothing requires network.target or the legacy $network SysV capability.
* systemd: pull in network.service and introduce ↵Lennart Poettering2011-04-063-4/+24
| | | | | | | | | | | | | | | | | | NetworkManager-wait-online.service This pulls in network.target from NetworkManager.service (and not the other way round), as suggested and agreed on on the systemd ML: http://lists.freedesktop.org/archives/systemd-devel/2011-March/001692.html This also introduces an auxiliary service NetworkManager-wait-online.service that can be used to order a unit after the point where the network is available. When this is enabled with "systemd enable NetworkManager-wait-online.service" the unit network.target will be delayed until the network is up, which is suitable for synchronizing NFS mounts and similar to it. https://bugzilla.redhat.com/show_bug.cgi?id=692008
* core: more systemd service file fixesDan Williams2010-08-182-2/+2
|
* core: add systemd unit supportDan Williams2010-08-123-0/+49
View Lorry Controller Status