systemd/units/systemd-hostnamed.service.in

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Hostname Service
Documentation=man:systemd-hostnamed.service(8) man:hostname(5) man:machine-info(5)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/hostnamed

[Service]
ExecStart=@rootlibexecdir@/systemd-hostnamed
BusName=org.freedesktop.hostname1
CapabilityBoundingSet=CAP_SYS_ADMIN
WatchdogSec=1min
PrivateTmp=yes
PrivateDevices=yes
PrivateNetwork=yes
ReadOnlySystem=yes
ProtectedHome=yes
hostnamed: introduce systemd-hostnamed http://www.freedesktop.org/wiki/Software/systemd/hostnamed 2011-04-16 08:02:54 +08:00			`# This file is part of systemd.`
			`#`
			`# systemd is free software; you can redistribute it and/or modify it`
relicense to LGPLv2.1 (with exceptions) We finally got the OK from all contributors with non-trivial commits to relicense systemd from GPL2+ to LGPL2.1+. Some udev bits continue to be GPL2+ for now, but we are looking into relicensing them too, to allow free copy/paste of all code within systemd. The bits that used to be MIT continue to be MIT. The big benefit of the relicensing is that closed source code may now link against libsystemd-login.so and friends. 2012-04-12 06:20:58 +08:00			`# under the terms of the GNU Lesser General Public License as published by`
			`# the Free Software Foundation; either version 2.1 of the License, or`
hostnamed: introduce systemd-hostnamed http://www.freedesktop.org/wiki/Software/systemd/hostnamed 2011-04-16 08:02:54 +08:00			`# (at your option) any later version.`

			`[Unit]`
			`Description=Hostname Service`
man: document systemd-hostnamed 2012-06-26 06:04:50 +08:00			`Documentation=man:systemd-hostnamed.service(8) man:hostname(5) man:machine-info(5)`
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them. 2012-05-21 21:12:18 +08:00			`Documentation=http://www.freedesktop.org/wiki/Software/systemd/hostnamed`
hostnamed: introduce systemd-hostnamed http://www.freedesktop.org/wiki/Software/systemd/hostnamed 2011-04-16 08:02:54 +08:00
			`[Service]`
			`ExecStart=@rootlibexecdir@/systemd-hostnamed`
			`BusName=org.freedesktop.hostname1`
units: remove CAP_SYS_PTRACE capability from hostnamed/networkd The ptrace capability was only necessary to detect virtualizations environments. Since we changed the logic to determine this to not require priviliges, there's no need to carry the CAP_SYS_PTRACE capability anymore. 2014-06-01 14:54:09 +08:00			`CapabilityBoundingSet=CAP_SYS_ADMIN`
event: hook up sd-event with the service watchdog logic Adds a new call sd_event_set_watchdog() that can be used to hook up the event loop with the watchdog supervision logic of systemd. If enabled and $WATCHDOG_USEC is set the event loop will ping the invoking systemd daemon right after coming back from epoll_wait() but not more often than $WATCHDOG_USEC/4. The epoll_wait() will sleep no longer than $WATCHDOG_USEC/4*3, to make sure the service manager is called in time. This means that setting WatchdogSec= in a .service file and calling sd_event_set_watchdog() in your daemon is enough to hook it up with the watchdog logic. 2013-12-12 01:14:52 +08:00			`WatchdogSec=1min`
units: make use of PrivateTmp=yes and PrivateDevices=yes for all our long-running daemons 2014-03-19 23:45:28 +08:00			`PrivateTmp=yes`
			`PrivateDevices=yes`
core: enable PrivateNetwork= for a number of our long running services where this is useful 2014-03-20 06:08:39 +08:00			`PrivateNetwork=yes`
core: add new ReadOnlySystem= and ProtectedHome= settings for service units ReadOnlySystem= uses fs namespaces to mount /usr and /boot read-only for a service. ProtectedHome= uses fs namespaces to mount /home and /run/user inaccessible or read-only for a service. This patch also enables these settings for all our long-running services. Together they should be good building block for a minimal service sandbox, removing the ability for services to modify the operating system or access the user's private data. 2014-06-04 05:41:44 +08:00			`ReadOnlySystem=yes`
			`ProtectedHome=yes`