/var/run/sks not presistent across reboot

[Andy Ruddock]

Binary package hint: sks

1. Ubuntu release :
Description: Ubuntu 8.10
Release: 8.10

2. Package version :
sks:
  Installed: 1.1.0-3
  Candidate: 1.1.0-3
  Version table:
 *** 1.1.0-3 0
        500 http://no.archive.ubuntu.com intrepid/universe Packages
        100 /var/lib/dpkg/status

3. sks uses the directory /var/run/sks owned by user debian-sks to store pid files. this directory is not persistent across reboots and should be recreated in the init.d script.

4. As it currently stands sks will not start after a reboot as the /var/run/sks directory does not exist.

[dingdong (happygnr)]

The problem is, that /var/run/sks just does not exist.

[Andy Ruddock (andy-ruddock)]

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 is run, rather than including them in the package and relying on dpkg to create them."

which is why I suggest in the bug report that /var/run/sks be created in the init.d script - which is indeed what I have done as a fix for this bug.

[Jean-Baptiste Lallement (jibel)]

Thanks for your report.

This particular bug has been fixed in sks 1.1.0-5 available since lucid.

[Dan Egli (funkydan)]

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 askubuntu.com (before I knew to post here). The url is:
https://askubuntu.com/questions/1272980/bug-in-ubuntu-20-04-ltss-sks-package