summaryrefslogtreecommitdiff
path: root/units/basic.target
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #2565 from poettering/fix-2315Zbigniew Jędrzejewski-Szmek2016-02-091-3/+6
|\
| * units: downgrade dependency on /tmp in basic.target to Wants=Lennart Poettering2016-02-091-4/+6
|/ | | | | | | Now that requiring of a masked unit results in failure again, downgrade the dependency on /tmp to Wants= again, so that our suggested way to disable /tmp-on-tmpfs by masking doesn't result in a failing boot. References: #2315
* units: explicitly require /var, /tmp and /var/tmp to be mounted before ↵Lennart Poettering2015-04-031-3/+5
| | | | | | | | | | | | basic.target We support /var, /tmp and /var/tmp on NFS. NFS shares however are by default ordered only before remote-fs.target which is a late-boot service. /var, /tmp, /var/tmp need to be around earlier though, hence explicitly order them before basic.target. Note that this change simply makes explicit what was implicit before, since many early-boot services pulled in parts of /var anyway early.
* units: disable job timeoutsZbigniew Jędrzejewski-Szmek2014-11-051-3/+0
| | | | | | | | | | | | | For boot, we might kill fsck in the middle, with likely catastrophic consequences. On shutdown there might be other jobs, like downloading of updates for installation, and other custom jobs. It seems better to schedule an individual timeout on each one separately, when it is known what timeout is useful. Disable the timeouts for now, until we have a clearer picture of how we can deal with long-running jobs.
* unit: do not order timers.target before basic.targetZbigniew Jędrzejewski-Szmek2014-11-021-1/+4
| | | | | | | | | | | | | | | | | | | | | | Since commit 19f8d037833f2 'timer: order OnCalendar units after timer-sync.target if DefaultDependencies=no' timers might get a dependency on time-sync.target, which does not really belong in early boot. If ntp is enabled, time-sync.target might be delayed until a network connection is established. It turns out that majority of timer units found in the wild do not need to be started in early boot. Out of the timer units available in Fedora 21, only systemd-readahead-done.timer and mdadm-last-resort@.timer should be started early, but they both have DefaultDependencies=no, so are not part of timers.target anyway. All the rest look like they will be fine with being started a bit later (and the majority even much later, since they run daily or weekly). Let timers.target be pulled in by basic.target, but without the temporal dependency. This means timer units are started on a "best effort" schedule. https://bugzilla.redhat.com/show_bug.cgi?id=1158206
* units: define appropriate job timeout actions when boot or shutdown timeouts ↵Lennart Poettering2014-10-281-0/+2
| | | | | | | | | | | are hit Using the new JobTimeoutAction= setting make sure we power off the machine after basic.target is queued for longer than 15min but not executed. Similar, if poweroff.target is queued for longer than 30min but does not complete, forcibly turn off the system. Similar, if reboot.target is queued for longer than 30min but does not complete, forcibly reboot the system.
* units: remove RefuseManualStart from units which are always aroundZbigniew Jędrzejewski-Szmek2014-06-281-1/+0
| | | | | | | | | | | | | | | In a normal running system, non-passive targets and units used during early bootup are always started. So refusing "manual start" for them doesn't make any difference, because a "start" command doesn't cause any action. In early boot however, the administrator might want to start on of those targets or services by hand. We shouldn't interfere with that. Note: in case of systemd-tmpfiles-setup.service, really running the unit after system is up would break the system. So e.g. restarting should not be allowed. The unit has "RefuseManualStop=yes", which prevents restart too.
* units: add default units for system.slice, user.slice, machine.sliceLennart Poettering2013-06-181-2/+2
|
* units: downgrade dependency on sockets.target/timers.target/paths.target by ↵Lennart Poettering2013-03-261-1/+2
| | | | | | | | basic.target There isn't really any need to require any targets but sysinit.target from basic.target, so downgrade sockets.target, paths.target, timers.target.
* units: introduce new timers.target and paths.target to hook timer/path units ↵Lennart Poettering2013-03-251-2/+2
| | | | into for boot
* units: introduce new Documentation= field and make use of it everywhereLennart Poettering2012-05-211-2/+1
| | | | | | | | | | 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.
* relicense to LGPLv2.1 (with exceptions)Lennart Poettering2012-04-121-2/+2
| | | | | | | | | | | | | | 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.
* units: make fedora/single.service standard and rename it to rescue.serviceLennart Poettering2010-10-291-2/+2
|
* unit: rename OnlyByDependency= to RefuseManualStart= and introduce ↵Lennart Poettering2010-08-111-1/+1
| | | | | | | | RefuseManualStop= Some unit shall never be start on user request (e.g. shutdown.target) others never be stopped on user request (e.g. auditd.servce), hence offer options for both.
* units: introduce and explain sysinit.targetLennart Poettering2010-06-041-0/+14
View Lorry Controller Status