PidFile - create and manage a PID file from the BEAM process

[OvermindDL1]

@hauleth

then all other spawned processes should go down with it.

As I recall it doesn’t fork epmd from itself, but actually calls it from init, so I’m more unsure if it would work directly like that? Might have to give a specific systemd option to enforce that in the service file?

[hauleth]

@OvermindDL1

I’m more unsure if it would work directly like that? Might have to give a specific systemd option to enforce that in the service file?

It is probably socket activated (that is how it works in Ubuntu at least), so there is nothing defined in that unit, as there is no need for it to be defined.

And by the way, I highly suggest not using forking unit type and instead spawn services in the foreground

[OvermindDL1]

@hauleth

And by the way, I highly suggest not using forking unit type and instead spawn services in the foreground

Yep, my current file uses foreground but I originally used forking because of some issues around the beam and foreground daemon’s at the time. Regardless I think PidFile is mostly antiquated anymore anyway, distillary/releases I think have the functionality built in now?