summaryrefslogtreecommitdiffstats
path: root/units/user (unfollow)
Commit message (Collapse)AuthorFilesLines
2016-05-09networkd: reworkd LLDP emission to allow control of propagation levelLennart Poettering7-41/+126
This allows selecting the propagation level of emitted LLDP packets (specifically: the destination MAC address of the packets). This is useful because it allows generating LLDP packets that optionally cross certain types of bridges. See 802.11ab-2009, Table 7-1 for details.
2016-05-09tree-wide: port more code to use ifname_valid()Lennart Poettering8-85/+83
2016-05-09man: add documentation for the new --network-zone= concept of nspawnLennart Poettering2-1/+40
2016-05-09network: add automatic configuration for the networks created by nspawn ↵Lennart Poettering4-1/+32
--network-zone= This way, they "just work", similar to --network-veth behaves, as long as networkd is enabled and running on all involved nodes.
2016-05-09nspawn: add new --network-zone= switch for automatically managed bridge devicesLennart Poettering6-43/+235
This adds a new concept of network "zones", which are little more than bridge devices that are automatically managed by nspawn: when the first container referencing a bridge is started, the bridge device is created, when the last container referencing it is removed the bridge device is removed again. Besides this logic --network-zone= is pretty much identical to --network-bridge=. The usecase for this is to make it easy to run multiple related containers (think MySQL in one and Apache in another) in a common, named virtual Ethernet broadcast zone, that only exists as long as one of them is running, and fully automatically managed otherwise.
2016-05-09util-lib: add new ifname_valid() call that validates interface namesLennart Poettering5-2/+93
Make use of this in nspawn at a couple of places. A later commit should port more code over to this, including networkd.
2016-05-09man: document that nspawn's host0 and ve-* interfaces have default config in ↵Lennart Poettering1-15/+21
networkd
2016-05-09TEST-08: make sure / is remounted rwZbigniew Jędrzejewski-Szmek1-0/+14
In this test /etc/fstab is replaced by -.mount unit. This causes systemd-remount-fs.service to not remount / rw, which in turn causes various failures becuase /var is not writable. In particular systemd-tmpfiles-setup.service reports many failures. This is something to possibly fix on its own (see https://github.com/systemd/systemd/issues/791); in the meanwhile let's fix this test so that it doesn't fail, since the point of the test is to check aliases on mount units, and not a ro root.
2016-05-09tests: enable logging for pid1, disable for other systemd servicesZbigniew Jędrzejewski-Szmek1-1/+3
systemd-udev generated an insane amount of log output at debug level. It would break TEST-02-CRYPTSETUP by filling the overflowing the disk (which seems to be a bug in itself!).
2016-05-09tests: allow root to login with empty password to test imagesZbigniew Jędrzejewski-Szmek1-0/+3
2016-05-09tree-wide: remove uses of --failedZbigniew Jędrzejewski-Szmek4-5/+4
It has been replaced by --state=failed.
2016-05-09tests: specify format=raw for qemu to avoid warningZbigniew Jędrzejewski-Szmek1-1/+2
WARNING: Image format was not specified for '/var/tmp/systemd-test.tGi3od/rootdisk.img' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. Also use unsafe caching mode, we don't care about data integrity here.
2016-05-07NEWS: typo fix and american english (#3219)Thomas H. P. Andersen1-2/+2
2016-05-07NEWS: machinectl and loginctl also support --valueZbigniew Jędrzejewski-Szmek1-7/+8
2016-05-07systemctl: do not print header if no units will be listedZbigniew Jędrzejewski-Szmek1-1/+1
"0 units listed." is still printed.
2016-05-07systemctl: rewrite code to explicitly take care of n_units==0 caseZbigniew Jędrzejewski-Szmek1-4/+3
Coverity was complaing, but it was a false positive (CID #1354669). Nevertheless, it's better to rewrite the code so that units is never null.
2016-05-07NEWS: minor fixesDaniele Medri1-2/+2
2016-05-07italian: .po updatesDaniele Medri1-61/+77
2016-05-06tests: add test for #3171 (#3206)Evgeny Vereshchagin3-0/+109
2016-05-06core: dump TriggerLimitIntervalSec and TriggerLimitBurst tooEvgeny Vereshchagin1-0/+6
2016-05-06core: expose TriggerLimitIntervalUSecEvgeny Vereshchagin1-1/+1
Before: $ systemctl show --property TriggerLimitIntervalSec test.socket TriggerLimitIntervalSec=2000000 After: $ systemctl show --property TriggerLimitIntervalUSec test.socket TriggerLimitIntervalUSec=2s
2016-05-06core: update the right mtime after finishing writing of transient units (#3203)Lennart Poettering1-1/+1
Fixes: #3194
2016-05-06man: link the part about [DHCP] to the DHCP= explanationLennart Poettering1-0/+3
2016-05-06man: move IPv6 note to the right sectionLennart Poettering1-9/+5
Make the XML validate again.
2016-05-06networkd: move the IAID configuration option into the [DHCP] sectionLennart Poettering2-7/+8
It's only relevant to DHCP, and it should be where the DUID is configured too.
2016-05-06systemctl: indentation fixLennart Poettering1-14/+15
2016-05-06NEWS: bring NEWS a bit up-to-dateLennart Poettering2-46/+127
2016-05-06core: rework how we flush incoming traffic when a socket unit goes downLennart Poettering4-20/+66
Previously, we'd simply close and reopen the socket file descriptors. This is problematic however, as we won't transition through the SOCKET_CHOWN state then, and thus the file ownership won't be correct for the sockets. Rework the flushing logic, and actually read any queued data from the sockets for flushing, and accept any queued messages and disconnect them.
2016-05-06core: don't implicit open missing socket fds on daemon reloadLennart Poettering1-8/+46
Previously, when the daemon was reloaded and the configuration of a socket unit file was changed so that a different set of socket ports was defined for the socket we'd simply reopen the socket fds not yet open. This is problematic however, as this means the SOCKET_CHOWN state is not run for them, and thus their UID/GID is not corrected. With this change, don't open the missing file descriptors, but log about this issue, and ask the user to restart the socket explicit, to make sure all missing fds are opened. Fixes: #3171
2016-05-06core: split out selinux label retrieval logic into a function of its ownLennart Poettering1-30/+49
This should bring no behavioural change.
2016-05-06networkd: route fix commentSusant Sahani1-1/+1
2016-05-06networkd: cleanup FOREACH_WORDSusant Sahani1-38/+39
2016-05-05logind: drop pointless UINT64_C() macro useLennart Poettering1-3/+3
2016-05-05logind: enforce a limit on inhibitors we hand outLennart Poettering6-0/+34
For similar reasons as the recent addition of a limit on sessions. Note that we don't enforce a limit on inhibitors per-user currently, but there's an implicit one, since each inhibitor takes up one fd, and fds are limited via RLIMIT_NOFILE, and the limit on the number of processes per user.
2016-05-05logind: expose more configuration settings as bus propertiesLennart Poettering1-0/+3
2016-05-05logind: don't include session lists in PropertyChanged messagesLennart Poettering2-2/+2
If we have a lot of simultaneous sessions we really shouldn't send the full list of active sessions with each PropertyChanged message for user and seat objects, as that can become quite substantial data, we probably shouldn't dump on the bus on each login and logout. Note that the global list of sessions doesn't send out changes like this either, it only supports requesting the session list with ListSessions(). If cients want to get notified about sessions coming and going they should subscribe to SessionNew and SessionRemoved signals, and clients generally do that already. This is kind of an API break, but then again the fact that this was included was never documented.
2016-05-05logind: process session/inhibitor fds at higher priorityLennart Poettering3-3/+5
Let's make sure we process session and inhibitor pipe fds (that signal sessions/inhibtors going away) at a higher priority than new bus calls that might create new sessions or inhibitors. This helps ensuring that the number of open sessions stays minimal.
2016-05-05update TODOLennart Poettering1-0/+4
2016-05-05logind: enforce a limit on current user sessionsLennart Poettering6-0/+36
We really should put limits on all resources we manage, hence add one to the number of concurrent sessions, too. This was previously unbounded, hence set a relatively high limit of 8K by default. Note that most PAM setups will actually invoke pam_systemd prefixed with "-", so that the return code of pam_systemd is ignored, and the login attempt succeeds anyway. On systems like this the session will be created but is not tracked by systemd.
2016-05-05update TODOLennart Poettering1-0/+2
2016-05-05core: fix owner user/group output in socket dumpLennart Poettering1-4/+5
The unit file settings are called SocketUser= and SocketGroup= hence name these fields that way in the "systemd-analyze dump" output too. https://github.com/systemd/systemd/issues/3171#issuecomment-216216995
2016-05-05core: change default trigger limits for socket unitsLennart Poettering2-7/+28
Let's lower the default values a bit, and pick different defaults for Accept=yes and Accept=no sockets. Fixes: #3167
2016-05-05journald: stack allocation cannot failLennart Poettering1-10/+8
No need to check whether alloca() failed...
2016-05-05tree-wide: introduce new SOCKADDR_UN_LEN() macro, and use it everywhereLennart Poettering23-75/+87
The macro determines the right length of a AF_UNIX "struct sockaddr_un" to pass to connect() or bind(). It automatically figures out if the socket refers to an abstract namespace socket, or a socket in the file system, and properly handles the full length of the path field. This macro is not only safer, but also simpler to use, than the usual offsetof() + strlen() logic.
2016-05-05test-networkd-conf: fix memleakThomas Hindoe Paaboel Andersen1-1/+3
2016-05-05networkd: fix memleak in config_parse_duid_rawdataThomas Hindoe Paaboel Andersen1-1/+1
2016-05-05core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notificationLennart Poettering6-78/+209
dbus-daemon currently uses a backlog of 30 on its D-bus system bus socket. On overloaded systems this means that only 30 connections may be queued without dbus-daemon processing them before further connection attempts fail. Our cgroups-agent binary so far used D-Bus for its messaging, and hitting this limit hence may result in us losing cgroup empty messages. This patch adds a seperate cgroup agent socket of type AF_UNIX/SOCK_DGRAM. Since sockets of these types need no connection set up, no listen() backlog applies. Our cgroup-agent binary will hence simply block as long as it can't enqueue its datagram message, so that we won't lose cgroup empty messages as likely anymore. This also rearranges the ordering of the processing of SIGCHLD signals, service notification messages (sd_notify()...) and the two types of cgroup notifications (inotify for the unified hierarchy support, and agent for the classic hierarchy support). We now always process events for these in the following order: 1. service notification messages (SD_EVENT_PRIORITY_NORMAL-7) 2. SIGCHLD signals (SD_EVENT_PRIORITY_NORMAL-6) 3. cgroup inotify and cgroup agent (SD_EVENT_PRIORITY_NORMAL-5) This is because when receiving SIGCHLD we invalidate PID information, which we need to process the service notification messages which are bound to PIDs. Hence the order between the first two items. And we want to process SIGCHLD metadata to detect whether a service is gone, before using cgroup notifications, to decide when a service is gone, since the former carries more useful metadata. Related to this: https://bugs.freedesktop.org/show_bug.cgi?id=95264 https://github.com/systemd/systemd/issues/1961
2016-05-05Trivial network cleanup (#3196)Thomas H. P. Andersen2-2/+1
* gitignore: typo fix for test-networkd-conf * networkd: fix double include
2016-05-04core: fix segfault on "systemctl --set-property UNIT BlockIODeviceWeight=WEIGHT"Tejun Heo1-1/+1
bus_append_unit_property_assignment() was missing an argument for sd_bus_message_append() when processing BlockIODeviceWeight leading to segfault. Fix it. Signed-off-by: Tejun Heo <htejun@fb.com>
2016-05-04treewide: fix typos (#3187)Torstein Husebø5-6/+6
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 07:00:16 +0100