summaryrefslogtreecommitdiff
path: root/src/systemctl/systemctl.c
diff options
context:
space:
mode:
authorMichal Schmidt <mschmidt@redhat.com>2013-02-15 22:42:26 +0100
committerMichal Schmidt <mschmidt@redhat.com>2013-02-16 01:18:09 +0100
commit9d246da3c630559924a0262769c8493fa22c7acc (patch)
tree4ba7227e8b07f348ee1f50512273a8d42bde457b /src/systemctl/systemctl.c
parent80cbda3558c534b575bf5315fa53b0f82dc088ab (diff)
unit: don't Require systemd-journald.socket from units
It is not really necessary to have a hard requirement dependency on systemd-journald.socket in almost every unit. The socket gets pulled into boot via at least two ways: sockets.target -> systemd-journald.socket sysinit.target -> systemd-journald.service -> systemd-journald.socket So just assume something pulled the socket in and drop the automatic requirement dependencies on it. "systemctl stop systemd-journald.socket" will now not take the whole system down with it.
Diffstat (limited to 'src/systemctl/systemctl.c')
0 files changed, 0 insertions, 0 deletions