Re: (Exposing?) config files and non-start/stop operations

[Ludovic Courtès]

Christopher Allan Webber <address@hidden> skribis:

> Anyway, I think exposing the `actions' slot in shepherd is the way to
> go.  We could already use it for some things other than the theoretical
> examples I've given.  Last night I wanted to do something like:
>
>   sudo mcron --schedule=10
>
> ... which would, according to the mcron docs, show me the next ten
> upcoming tasks that are scheduled!  I wanted to verify that I was
> writing my mcron procedures right.  Likewise, my shepherd configuration
> seems obscured (well sort of, I can figure it out by looking at
> `ps auwwwx' but I don't want to do that).  It would be nice if I could
> do:
>
>   sudo herd list-schedule mcron 10
>
> Anyway, hopefully I've made my case! :)

Definitely!  :-)  This one is a good example, too.

Ludo’.