I am curious to hear about the context of your tests : my Zesty system with a separated /var does show the problem prior to upgrade to unattended-upgrades-0.93.1ubuntu2 and no longer hangs when the new package is applied. There might be situations that I have not tested where the issue could still exists.
Your suggestion to replace /var/run by /var is incorrect : /var/run/unattended-upgrades.lock is placed by the unattended-upgrades script; Looking in /run for a lock file that has been put in /var/run is simply inadequate.
While replacing /var/run by /run across the board is a valid proposition, it requires more inspection than simply replacing its occurrences in one script.
Hello,
I am curious to hear about the context of your tests : my Zesty system with a separated /var does show the problem prior to upgrade to unattended- upgrades- 0.93.1ubuntu2 and no longer hangs when the new package is applied. There might be situations that I have not tested where the issue could still exists.
Your suggestion to replace /var/run by /var is incorrect : /var/run/ unattended- upgrades. lock is placed by the unattended-upgrades script; Looking in /run for a lock file that has been put in /var/run is simply inadequate.
While replacing /var/run by /run across the board is a valid proposition, it requires more inspection than simply replacing its occurrences in one script.