run-one lock

[Markus Zeller]

It looks like the lock files of the "run-one" command have not been deleted (maybe at reboot?). I was wondering why a cronjob invoked was not running (every 5 minutes) anymore.

Sadly nothing were logged in the syslog (or I did not find it).

After removing it worked like a charm, again.

[Joshua Powers (powersj)]

Hi Markus, thanks for taking the time to file a bug. This doesn't appear to be a bug against the Ubuntu man page repository, but instead possibly against the run-one command. I've added that task to this bug and marked the manpage repo invalid.

Could you also provide what version of Ubuntu you are using to help the run-one developers debug your issue?

Thanks!

[Markus Zeller (markuszeller)]

Thank you, Joshua. Yes, I do mean the "run-one" command, not the manpage. Maybe it is not even a "bug", but I sadly faced that problem.

I am using:
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

[Christian Ehrhardt  (paelzer)]

It does not clean the locks at all (it explicitly re-uses old lock DIRs)

Only if not found it does generate them as
        DIR=$(mktemp -d "/dev/shm/${PROG}_${USER}_XXXXXXXX")
        DIR="${DIR}/.cache/${PROG}"
And from there on continue to use them, but those are actually just directories.

that is tmpfs:
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)

Which implies that it is cleared on reboot (as it is only in memory).
You'll need to outline more what the problem is to understand your problem.

Furthermore the upstream project wasn't touched since 2013, not sure there is too much activity still.