Vivek Khera wrote:
And you know for certain that no other files were corrupted and
horribly broken? I don't.
Some of us live on the edge, and bank on the file system to repair
itself during bootup (mine do.). I have 12 servers running 24/7 and I
have yet to worry about any of them getting h
> "WY" == Will Yardley <[EMAIL PROTECTED]> writes:
>> When the system goes down uncleanly, you *want* manual intervention to
>> ensure things are really ok. Otherwise, why bother even having that
>> check in place?
WY> In theory, perhaps. But in reality, what we want is for Mailman to
WY> st
On Fri, Dec 12, 2003 at 03:39:24PM -0500, Vivek Khera wrote:
> Will Yardley <[EMAIL PROTECTED]> writes:
>
> > What do most folks do so that Mailman will restart when the system is
> > restarted uncleanly? Could having the system's startup script (assuming
> > a FreeBSD style or SysV style startup
> "WY" == Will Yardley <[EMAIL PROTECTED]> writes:
WY> What do most folks do so that Mailman will restart when the system is
WY> restarted uncleanly? Could having the system's startup script (assuming
WY> a FreeBSD style or SysV style startup script) default to "-s" cause any
WY> major problem
On Fri, Dec 12, 2003 at 03:16:04PM -0500, Todd wrote:
> Will Yardley wrote:
> > When mailmanctl is run with "-s" (supposedly kills stale locks),
> > Mailman spits out the default usage summary, and then "No command
> > given.". Same with "--stale-lock-cleanup". This command also fails
> > to clean
