run-one lock
Bug #1821807 reported by
Markus Zeller
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Manpage Repository |
Invalid
|
Undecided
|
Unassigned | ||
run-one |
New
|
Undecided
|
Unassigned | ||
run-one (Ubuntu) |
Incomplete
|
High
|
Unassigned |
Bug Description
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.
tags: | added: server-triage-discuss |
Changed in run-one (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | removed: server-triage-discuss |
tags: | added: server-triage-discuss |
Changed in run-one (Ubuntu): | |
status: | Triaged → Incomplete |
tags: | removed: server-triage-discuss |
tags: | added: server-triage-discuss |
tags: | removed: server-triage-discuss |
To post a comment you must log in.
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!