History log of /systemd/units/user@.service.m4.in
Revision Date Author Comments Expand
8c277ddd275607a17be4e7d322158e8e17004daf 22-Nov-2015 Jan Alexander Steffens (heftig) <jan.steffens@gmail.com>

Set user@.service TasksMax=infinity The user manager is still limited by its parent slice user-UID.slice, which defaults to 4096 tasks. However, it no longer has an additional limit of 512 tasks. Fixes #1955.

cf5a8997515dc5fc96f34385ad153e4b213b4705 14-Dec-2014 Mantas MikulÄ—nas <grawity@gmail.com>

build-sys: remove commented-out m4 from user@.service Otherwise this actually remains in the generated unit in /usr/lib. If you want to keep it commented out, a m4-compatible way would be: m4_ifdef(`HAVE_SMACK', dnl Capabilities=cap_mac_admin=i dnl SecureBits=keep-caps )

1f3ba2bb4f65b56ee77b098d8ab34766db55cf0a 10-Dec-2014 Lennart Poettering <lennart@poettering.net>

build-sys: turn off SMACK capabilities stuff for now, since it is incompatible with nspawn

dd5ae4c36c89da5dbe8d1628939b26c00db98753 09-Dec-2014 Przemyslaw Kedzierski <p.kedzierski@samsung.com>

bus-proxy: cloning smack label When dbus client connects to systemd-bus-proxyd through Unix domain socket proxy takes client's smack label and sets for itself. It is done before and independent of dropping privileges. The reason of such soluton is fact that tests of access rights performed by lsm may take place inside kernel, not only in userspace of recipient of message. The bus-proxyd needs CAP_MAC_ADMIN to manipulate its label. In case of systemd running in system mode, CAP_MAC_ADMIN should be added to CapabilityBoundingSet in service file of bus-proxyd. In case of systemd running in user mode ('systemd --user') it can be achieved by addition Capabilities=cap_mac_admin=i and SecureBits=keep-caps to user@.service file and setting cap_mac_admin+ei on bus-proxyd binary.

4acbce79798347cddf1e1d42e9be571e0a041873 27-Dec-2013 Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>

build-sys: fix generation of user@.service