All the lock files have been deleted as I found no process running for any of them. However, the problem still occurs. What should I attempt next?
Thanks. On Tue, Jul 22, 2014 at 5:29 PM, Mark Sapiro <[email protected]> wrote: > On 07/22/2014 02:20 PM, Chad Rebuck wrote: > > Should I delete each lock in order from oldest to newest, excluding the > > active lock (20307)? I've deleted a few and waited a few minutes > > between each delete and saw no locks auto disappear yet. > > > You can go through the whole list looking for non-existent PIDs and > delete all those, or you can delete just the active lock as that is the > one preventing the others from proceeding. > > I.e., delete the active lock (assuming its PID is gone) and some waiting > processes may proceed. In any case, a new lock will become active. > Repeat that until no locks remain. > > > > Would I delete a2-16v-list.lock is I make it down the list that far > > should I leave it alone? > > If at some point you are left with only the a2-16v-list.lock and no > a2-16v-list.lock.pogo.PID.* files, you can just remove a2-16v-list.lock, > or I think if you don't, it will be automatically removed the next time > a process locks and unlocks the a2-16v-list list. > > -- > Mark Sapiro <[email protected]> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ Mailman-Users mailing list [email protected] https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
