18 Feb
2021
18 Feb
'21
6:26 a.m.
Guillermo Hernandez (Oldno7) via Mailman-users writes:
On 17/2/21 18:11, Gelpi Andrea wrote:
For some unknown reason in /var/lib/mailman3/lock there was a file master.lck.
I simply rename it and now mailman3 starts.
It happens when mailman doesn't close cleanly. You can use the --force param to start it and avoid the lock.
Thanks, Guillermo!
Notes: The lockfile should be an invisible implementation detail, but it isn't for historical reasons. I think simply removing the lock is safe for Mailman currently, but when a "--force" (better name would be "--override-locks") option is available, please use it. And if you don't know, check. The option, being built in to the application, will try to avoid any pitfalls of the brute-force approach.
Steve