I installed a bacula-fd client on a machine. This was done through a make install, and make install-autostart-fd, that generated a /etc/init.d/bacula-fd
Now running /etc/init.d/bacula-fd start runs nicely, and starts the daemon. On the contrary, systemctl start bacula-fd does not start anything, and the service permanently says active(exited).
As far as I understand systemd, a
systemctl list-unit-files --type=service
and in fact I can find inside /run/systemd/generator.late a file that has
ExecStart=/etc/init.d/bacula-fd start ExecStop=/etc/init.d/bacula-fd stop
So the question is why can I run it directly successfully, but not through systemctl?
Thanks for any hint, hj
Some more info, if I ask the status, the status from 2hrs ago is displayed, but I just started the service now (2 min ago). This is puzzling me also.
systemctl status bacula-fd ● bacula-fd.service - LSB: Bacula File Daemon Loaded: loaded (/etc/init.d/bacula-fd; generated) Active: active (exited) since Sun 2018-12-23 17:23:48 CET; 2h 4min ago Docs: man:systemd-sysv-generator(8) Main PID: 2811 (code=exited, status=15) Tasks: 0 (limit: 19660) CGroup: /system.slice/bacula-fd.service Dec 23 17:23:48 hostname systemd: Starting LSB: Bacula File Daemon... Dec 23 17:23:48 hostname systemd: Started LSB: Bacula File Daemon.