[ mailman-Patches-1208685 ] mailmanctl report status

[SourceForge.net]

Patches item #1208685, was opened at 2005-05-25 15:16
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1208685&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: command line scripts
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: John Dennis (jdennis-redhat)
Assigned to: Nobody/Anonymous (nobody)
Summary: mailmanctl report status

Initial Comment:
Mark's point about the presence of the pid and lock
files not being a definitive
metric of mailman health should not be ignored. You
really have to
ascertain the status of the process. If mailman is
abnormally aborting,
which is what started this thread, then there is a high
degree of
probably the lock files will be left behind and testing
them will give
false positives.

In the Red Hat mailman RPM's we've modified mailmanctl
so that it can be
asked the status of the mailman process as an
unprivledged user and
return the result as status to the shell as well as
printing a message.
Since mailmanctl knows how to locate the process and
communicate with
the process via signals it makes mailmanctl the optimal
reporter of
status. It was probably an oversight mailmanctl never
had this facility.
We have also integrated this with the mailman init.d
script so that one
can perform the standard "service mailman status"
command. The init.d
script depends on the exit status of "mailmanctl
status". These two
changes probably represent a more robust and standard
way to determine
status.

Two files are patched in this patch, mailmanctl and
mailman init.d script. Technically the init.d script
does not need to be modified to take advantage of the
mailmanctl status feature, but the two are really meant
to play together.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1208685&group_id=103