Hi all,
and thanks a lot for your attention.
The simple patch in attachment fix the problem, so it means
the bug is inside
/usr/lib/mailman/bin/mailmanctl
not in init script
/etc/init.d/mailman
I suppose there's a wrong implementation of flag '-s':
-s/--stale-lock-cleanup
If mailmanctl finds an existing master lock, it will normally exit
with an error message. With this option, mailmanctl will perform an
extra level of checking. If a process matching the host/pid described
in the lock file is running, mailmanctl will still exit, but if no
matching process is found, mailmanctl will remove the apparently stale
lock and make another attempt to claim the master lock.
Thanks a lot for your work,
Andrea
** Patch added: "Avoid buggy '-s' implementation"
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/651182/+attachment/1667136/+files/fix.patch
--
Invocations of "/etc/init.d/mailman start" spawns multiple instances
https://bugs.launchpad.net/bugs/651182
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
