[Bug 925559] [NEW] Mailman Masterrunner keeps locks after force

benste 925559 at bugs.launchpad.net
Thu Feb 2 17:20:52 CET 2012


Public bug reported:

I've existed Mailman just closing my terminal which didn't stop it
properly.

Since a8 I'm getting a message to use --force to start it which doesn't
delete the locks directory hence doesn't start it.

benste at benste-vpc-sb1c5e:~/Projects/Mailman/mailman-3.0.0a8$ bin/mailman start --force
usage: mailman [-h] [-v] [-C CONFIG]
               
               {help,aliases,create,import21,info,inject,lists,members,qfile,remove,reopen,restart,start,status,stop,unshunt,version,withlist}
               ...
mailman: error: A previous run of GNU Mailman did not exit cleanly.  Try using --force.


Deleting all files in ./locks enables me to start it again.

** Affects: mailman
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/925559

Title:
  Mailman Masterrunner keeps locks after force

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/925559/+subscriptions


More information about the Mailman-coders mailing list