[Expired for clamav (Ubuntu) because there has been no activity for 60
days.]
** Changed in: clamav (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624262
The systemd service these days doesn't use a pidfile at all anymore.
It uses "normal" systemd handling of a single process service which will
poulate $MAINPID that can be referenced from associated systemd services.
You can fetch those via:
systemctl show -p MainPID clamav-daemon
Actually it
I came by cleanin gup bugs that were dormant for too long, and I beg
your pardon for thise being that way. Yet I hope my explanation helps.
If you think this is really needed for former releases or if I missed
sometihng plese set back to new.
** Changed in: clamav (Ubuntu)
Status:
** Tags added: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624262
Title:
clamav unable to create pid file using systemd
To manage notifications about this bug go to:
Same here and in conjunction with Monit, causes lots of error log
entries
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624262
Title:
clamav unable to create pid file using systemd
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: clamav (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624262
Title:
I forgot to mention that the above solution works within our LXC guest
environments, but it is not sufficient when running on physical
hardware.
It seems, that the clamav startup scripts are executed a bit too early.
When they are started, the folder /run or /var/run is not yet a tmpfs.
So the
