[NiLuJe]

Originally Posted by pazos

I'm not sure about the purpose but you can always patch the runtime to provide an interface over cli and use that to call Device.exit(). See https://github.com/koreader/koreader...tches#overview

I imagine you'd need an RPC àla https://github.com/koreader/koreader/pull/10223 to control an *existing* instance.

Originally Posted by bitfreak

Koreader is running as a service

Irrelevant, as process monitoring won't do shit if what's being monitored doesn't care about SIGHUP . (Spoiler: we don't).

(Also wrong on nearly every platform, the only platform which uses a very very very very thin "service" shim is rM, but that's a technicality, as it doesn't do shit besides fire a one-off script that isn't actually KOReader yet).