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
n.b.: same fix on Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/651182
*** /tmp/mailman 2010-10-02 20:13:30.624148238 +0200
--- /etc/init.d/mailman 2010-10-02 20:13:39.000000000 +0200
***************
*** 54,60 ****
exit 0;
fi
log_daemon_msg "Starting Mailman master qrunner" "mailmanctl"
! if $DAEMON -s -q start; then
log_end_msg 0
else
log_end_msg 1
--- 54,60 ----
exit 0;
fi
log_daemon_msg "Starting Mailman master qrunner" "mailmanctl"
! if $DAEMON -q start; then
log_end_msg 0
else
log_end_msg 1
