JService is a system daemon responsible for making sure other services are running on a server.
Its job is to

Monitoring & management

JService itself is connected in real time to the monitoring system Loke, so any events or tampering attempts will be logged centrally.

JService accepts the following Loke remote commands:

To monitor physical hardware, the JLinux package ipmitool must be installed by the OS. JService will automatically enable hardware monitoring.

If the server support hardware watchdog, jservice will enable it. This means that if the OS or jservice crash or becomes unresponsive, the hardware will reboot the server.

Manual usage

Default application folder is /etc/app/j/service

Default application configuration folder is /etc/app/j/config

Any application that exists in the folder /etc/app/j/service will be executed and must continuously run without exiting to not trigger a monitoring alert.

Applications receive 1 parameter which is the configfile J-daemons normally use. For example, the daemon testdaemon will be executed as

To add or remove an application, make the necessary change to the files in /etc/app/j/service and send a HUP signal to the jservice daemon: killall -HUP jservice

If you removed a service, the application will receive a TERM signal followed by a KILL signal 10 seconds later if it did not exit.

To change an application or configfile you can just kill the application directly. Some applications support configfile reloading without restart.

Service manager - automated usage

Please see service manager documentation for how to structure jlinux packages