diff options
| author | Luke Shumaker <lukeshu@sbcglobal.net> | 2017-02-03 18:19:17 -0500 |
|---|---|---|
| committer | Luke Shumaker <lukeshu@sbcglobal.net> | 2017-02-03 18:19:17 -0500 |
| commit | 190b7b234cc69fdcf65aaaa0a763a73dfa58fe45 (patch) | |
| tree | 5cc8e0a8918804050f478008aac077b59934371c | |
| parent | 709b7aa21ec4f869d9ba0d2fa23b960320f03a97 (diff) | |
nshd.service.in: Fix a typo in a comment.
| -rw-r--r-- | nshd.service.in | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/nshd.service.in b/nshd.service.in index 7760687..6aa3d2f 100644 --- a/nshd.service.in +++ b/nshd.service.in @@ -19,7 +19,7 @@ Also=nshd.socket # The following is a workaround for a scheduling deadlock in systemd # v230 (and probably other versions). What "naturally" happens is # that we would be socket-activated by systemd-logind which is -# dbus-activated during systemd' dbus_init(), which is called when +# dbus-activated during systemd's dbus_init(), which is called when # dbus.service starts. However, systemd is buggy and won't activate # any services during dbus_init(), so the whole thing deadlocks. A # timeout means that boot eventually continues, but we are left with a |