author | Olivier Brunel
<jjk@jjacky.com> 2018-01-16 19:41:05 UTC |
committer | Olivier Brunel
<jjk@jjacky.com> 2018-01-19 17:37:19 UTC |
parent | 5f7fb68c3f4810e55820bf861da3617b94103c36 |
doc/aa-enable.pod | +3 | -3 |
diff --git a/doc/aa-enable.pod b/doc/aa-enable.pod index 432e8ec..a69af08 100644 --- a/doc/aa-enable.pod +++ b/doc/aa-enable.pod @@ -14,11 +14,11 @@ B<aa-enable> [B<-D>] [B<-r> I<REPODIR>] [B<-c> I<CRASH>] [B<-f> I<FINISH>] =item B<-a, --alarm-s6> -Alarms I<s6-svscan> as last step; This obviously assumes there is a running -instance of I<s6-svscan> running on I<REPODIR/.scandir>; Also note that it will +Alarms B<s6-svscan> as last step; This obviously assumes there is a running +instance of B<s6-svscan> running on I<REPODIR/.scandir>; Also note that it will do it regardless of whether longruns where added or not. -"Alarm" means I<s6-svscan> will immediately perform a scan of its scandir to +"Alarm" means B<s6-svscan> will immediately perform a scan of its scandir to check for (new) services. This is equivalent to manually running C<s6-svscan -a REPODIR/.scandir> afterwards.