Michael Jones wrote:
> On Fri, May 15, 2020 at 4:35 AM Petr Štetiar
> wrote:
>
> > Michael Jones [2020-05-15 02:39:52]:
> >
> > > What's wrong with monit is that it's documentation is gigantic
> >
> > Good documentation with a lot of examples is hardly a problem, its a bonus
> > point for me.
On Thu, May 14, 2020 at 5:56 PM Wes Turner wrote:
> FWIW, k8s has Liveness, Readiness and Startup Probes
>
> https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
> ::
>
> > The kubelet uses startup probes to know when a container application has
>
On Fri, May 15, 2020 at 9:57 AM Henrique de Moraes Holschuh
wrote:
> On 15/05/2020 03:58, Petr Štetiar wrote:
> > In other words I think, that one can solve this use case with current
> > solutions, no need to bloat procd.
>
> And if you're going to bloat procd, it pays to look at what the
>
On Fri, May 15, 2020 at 4:35 AM Petr Štetiar wrote:
> Michael Jones [2020-05-15 02:39:52]:
>
> > What's wrong with monit is that it's documentation is gigantic
>
> Good documentation with a lot of examples is hardly a problem, its a bonus
> point for me.
>
>
I think you misunderstood.
Monit
On 15/05/2020 03:58, Petr Štetiar wrote:
In other words I think, that one can solve this use case with current
solutions, no need to bloat procd.
And if you're going to bloat procd, it pays to look at what the
equivalent systemd functionality provides (it has a per-service
application-aware
Michael Jones [2020-05-15 02:39:52]:
> What's wrong with monit is that it's documentation is gigantic
Good documentation with a lot of examples is hardly a problem, its a bonus
point for me.
> for a relatively trivial need.
Your need, your current trivial use case. Overall project
On Fri, May 15, 2020 at 1:58 AM Petr Štetiar wrote:
> Michael Jones [2020-05-13 12:48:49]:
>
> Hi,
>
> > I have a critical service on my OpenWRT system that needs monitoring and
> > re-starting if it's failed.
>
> whats wrong with monit[1]? It was designed exactly for this purpose and is
> much
Michael Jones [2020-05-13 12:48:49]:
Hi,
> I have a critical service on my OpenWRT system that needs monitoring and
> re-starting if it's failed.
whats wrong with monit[1]? It was designed exactly for this purpose and is
much more flexible.
> I've been looking for a mechanism in procd that
On Thu, May 14, 2020, 23:43 Philip Prindeville <
philipp_s...@redfish-solutions.com> wrote:
>
> > On May 13, 2020, at 11:48 AM, Michael Jones
> wrote:
> >
> > I have a critical service on my OpenWRT system that needs monitoring and
> re-starting if it's failed.
> >
> > I've been looking for a
> On May 13, 2020, at 11:48 AM, Michael Jones wrote:
>
> I have a critical service on my OpenWRT system that needs monitoring and
> re-starting if it's failed.
>
> I've been looking for a mechanism in procd that would allow me to request
> that my service be terminated if it did not
FWIW, k8s has Liveness, Readiness and Startup Probes
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
::
> The kubelet uses startup probes to know when a container application has
started. If such a probe is configured, it disables liveness and
Hi,
I like the ubus watchdog ping/pong idea.
~ Jo
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On Wed, May 13, 2020 at 1:53 PM Eric Romano wrote:
> It does seem like process supervision would be a nice capability to
> have within procd.
>
> Previously I've done this by a combination of:
> 1. trying to crash / exit the process when an inconsistent state is hit.
> 2. monitoring for delayed
It does seem like process supervision would be a nice capability to
have within procd.
Previously I've done this by a combination of:
1. trying to crash / exit the process when an inconsistent state is hit.
2. monitoring for delayed writes to a timestamp pidfile in temp.
procd's respawn
I have a critical service on my OpenWRT system that needs monitoring and
re-starting if it's failed.
I've been looking for a mechanism in procd that would allow me to request
that my service be terminated if it did not periodically notify some
watchdog endpoint via ubus.
It seems to me like this
15 matches
Mail list logo
