Chris Kirke comments

Repositories
Issues
Comments

Results 2 comments of


                                            Chris Kirke

When there is a lockfile timeout, show the pid of the process that holds the lock

looks like File::NFSLock supports stale_lock_timeout, could expose it via PINTO_ env and document interaction if ultimate goal is not "wait forever" but "wait suitably long, then steal the lock" also,...

When there is a lockfile timeout, show the pid of the process that holds the lock

proposed https://github.com/hookbot/File-NFSLock/pull/3, if accepted, it should cover the reporting issue. continuing with the stale lock/steal lock portion of this.