5 thoughts
last posted Nov. 30, 2014, 11:24 p.m.

3 earlier thoughts


fleetd and systemd are still confusing me. TIL: There are definitely more state to a systemd and/or fleetd unit than simply 'start' and 'stopped'.

  • systemdActiveState: active/inactive/???
  • systemdLoadState: loaded/launched/???
  • systemdSubState: dead/running/failed/???

From what I gathered, a loaded/active/running state is what happens when a service is started as a dependency of another service. launched/active/running is what happens when a service is started manually with fleetctl start.

A launched/failed/failed can't simply be started, it must be loaded and started.

I am still trying to figure out how this effects the systemd.service Restart directive which I can not get to restart anything on non-zero exit codes.

I'm not 100% convinced many of the systemd features work alongside fleetd and docker. I was hopeful systemd would be my nanny process for ensuring crashed processes could be restarted, but I think it is time to introduce a new service into my test bed before I get too frustrated at systemd.

EDIT: Looks like Restart directive demands a timeout (RestartSecs), although I have not found the documentation that proves it.

1 later thought