Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 118117

systemd is an alternative approach to SystemV and Upstart init daemons for Linux. It is intended to provide a better framework for expressing services' dependencies, allow more work to be done in parallel at system startup, and to reduce shell overhead.

0
votes
This is a bug in systemd, where a service which fails all of its restarts gets listed as "inactive" rather than "failed". In my testing it occurs in 229 (default with Ubuntu Xenial), and is fixed in …
answered Apr 1 '18 by Edward Z. Yang
0
votes
1answer
, and then quiesce as a failed unit. However, this is what actually happens on systemd 229 with Ubuntu Xenial: root@monitoring:/etc/systemd/system# systemctl status foobar ● foobar.service - foobar … Loaded: loaded (/etc/systemd/system/foobar.service; disabled; vendor preset: Active: inactive (dead) Apr 01 21:08:43 monitoring.ci.ezyang.com systemd[1]: foobar.service: Service hol Apr 01 21 …
asked Apr 1 '18 by Edward Z. Yang
0
votes
This is a bug in systemd, and it is fixed systemd 238, and possibly earlier versions. [root@866d9b9835e0 system]# systemctl status foobar * foobar.service - foobar Loaded: loaded (/etc/systemd … =1/FAILURE) Main PID: 143 (code=exited, status=1/FAILURE) Apr 01 21:06:21 866d9b9835e0 systemd[1]: foobar.service: Service hold-off time over, scheduling restart. Apr 01 21:06:21 866d9b9835e0 systemd
answered Apr 1 '18 by Edward Z. Yang