On Sat, May 15 2021, raingloom wrote:
> Just throwing this out there:
> mcron is basically a very simple service manager, so, why not just move
> all its timer functionality into shepherd (like systemd's timer units)
> and then we can have a unified way to manage and debug services.
Yes please!
On 5/15/21 12:59 PM, Ludovic Courtès wrote:
raingloom skribis:
Or is everyone else happy with the current design and it's just me who
can't use Shepherd properly? 😅
I think it’s fair to say it’s rough on the edges. :-)
One thing that’s on the to-do list is switching to a real event loop in
On Sat, 15 May 2021 18:59:52 +0200
Ludovic Courtès wrote:
> > Security could also be improved probably. Can we have an OCAP model?
> > I feel like I don't know enough to say, so this mail is meant more
> > as a conversation starter.
>
> I think “having an ocap model” sounds nice but also vague
Hi!
raingloom skribis:
> Just throwing this out there:
> mcron is basically a very simple service manager, so, why not just move
> all its timer functionality into shepherd (like systemd's timer units)
> and then we can have a unified way to manage and debug services.
Yes, we could—see below.
Just throwing this out there:
mcron is basically a very simple service manager, so, why not just move
all its timer functionality into shepherd (like systemd's timer units)
and then we can have a unified way to manage and debug services.
But also, shepherd debugging is kind of terrible too, at lea
