I tried to reproduce it, but I failed.
Do you know of any command sequence that may reproduce the problem?
On Wed, Feb 01, 2017 at 02:26:06PM -0800, Richard Conner wrote:
> We recently came across an issue where taskspooler shows a job as running,
> but the referenced PID does not exist in the system.
> I *think* the process may have been SIGKILL (kill -9) and taskspooler never
> got a child exit signal and is left confused.
> The issue becomes more difficult if we have several very long running tasks
> that are queued up waiting to be executed.
> Is there any way of telling taskspooler that a long gone PID has finished?
> The only answer I can envision so far is to increase the taskspooler
> queue-size by 1 slot to account for the orphan slot and then restart
> taskspooler once all the tasks have been completed.
> You received this message because you are subscribed to the Google Groups "taskspooler" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to taskspooler...@googlegroups.com
> To post to this group, send an email to tasks...@googlegroups.com
> Visit this group at https://groups.google.com/group/taskspooler
> For more options, visit https://groups.google.com/d/optout
(Escriu-me xifrat si saps PGP / Write ciphered if you know PGP)
PGP key D4831A8A - https://emailselfdefense.fsf.org/