Greenbone Security Assistant 6.0.6 obviousely does not create a pidfile anymore. Therefore the initscript never reaches the "started" state. Status is "crashed". /usr/sbin/gsad --help does not show a pidfile option anymore either. Could we adjust the initfile accordingly?
thanks and cheers
I'm seeing the same problem with version 6.0.9. I'm managing this daemon from puppet and due to the "crashed" status puppet now tries to start the daemon on each run, even though it is running fine.
Openvas daemons isn't so well behaved.Also upstream don't provide init or systemd services default.
Upstream fixed this issue with latest 7.0.3 (currently in tree) but not properly.I had to fix it again for gentoo.
Normally pidfile must be generated by daemon when it is started.But their latest stables generates pidfile in build step and install them to /var/run manually. This behaivour breaks FHS/Gentoo policy paths.I changed this with patch.
I completly rewrited the init and systemd services for all openvas daemons ( including greenbone-security-assistant ) and fixed the issue with "command_background=true" option for openrc side.
This command creates pid file for automatically for you rather than the daemon itself being responsible for creating the PID file.
On systemd side it doesn't cause any error.