* Adding mdevd to the s6 boot process
@ 2024-12-09 23:58 Ian Macdonald via supervision
2024-12-10 2:11 ` Laurent Bercot
0 siblings, 1 reply; 2+ messages in thread
From: Ian Macdonald via supervision @ 2024-12-09 23:58 UTC (permalink / raw)
To: Ian Macdonald via supervision
Hi again,
Having got s6-linux-init and s6-rc to handle the ( early stage) boot
process, I decided, perhaps foolishly, to add mdevd to the mix.
Mdevd now warns 'unable to spawn ./run' every 60 seconds.
Any hints as to what ./run it is trying to run and where it should be?
Thanks
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Adding mdevd to the s6 boot process
2024-12-09 23:58 Adding mdevd to the s6 boot process Ian Macdonald via supervision
@ 2024-12-10 2:11 ` Laurent Bercot
0 siblings, 0 replies; 2+ messages in thread
From: Laurent Bercot @ 2024-12-10 2:11 UTC (permalink / raw)
To: Ian Macdonald via supervision
>Mdevd now warns 'unable to spawn ./run' every 60 seconds.
That sounds like something s6-supervise would write, not mdevd.
Are you sure it's related to mdevd? Check the service directories
you just added.
>Any hints as to what ./run it is trying to run and where it should be?
Typically it's the starting script of a longrun service, located in
a service directory.
We'd need the full, exact error message to be more precise - the
relevant information is in what you didn't say.
--
Laurent
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-12-10 2:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-12-09 23:58 Adding mdevd to the s6 boot process Ian Macdonald via supervision
2024-12-10 2:11 ` Laurent Bercot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).