That's not the case in 20.04 LTS. The bug is back apparently. Since
20.04 LTS uses Systemd, I created a script that fixes the directories
and a .service file to call it before sks or sks-recon. The new service
file and script are attached, in a simple zip file.
I detailed the whole thing on askubu
Thanks for your report.
This particular bug has been fixed in sks 1.1.0-5 available since lucid.
** Changed in: sks (Ubuntu)
Status: New => Fix Released
--
/var/run/sks not presistent across reboot
https://bugs.launchpad.net/bugs/313684
You received this bug notification because you are
I was given a pointer to the Ubuntu Policy Manual, in section 9.3.2 it
says
"In Ubuntu, /var/run is mounted as a temporary filesystem, so the init.d
scripts must handle this correctly. This will typically amount to
creating any required subdirectories of /var/run dynamically when the
init.d script
The problem is, that /var/run/sks just does not exist.
--
/var/run/sks not presistent across reboot
https://bugs.launchpad.net/bugs/313684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
