On Thu, 2009-06-25 at 09:45 +0000, Barry Warsaw wrote:
> It makes sense that if forster crashes, it would leave a stale Mailman
> pidfile laying around. I'll look into this, but the only thing I can
> think of is that the -s flag isn't getting passed to mailmanctl
> properly.
The initscript currently uses "make start" run from the root of the LP
tree.
Also, there are kind of two separate issues here - one is the not using
the -s flag as above. The other is that the pidfile is in the wrong
directory (/srv/launchpad.net/var rather
than /srv/lists.launchpad.net/var) - this means it takes longer for the
LOSA to find it and remove it as it's not in an expected location.
On Thu, 2009-06-25 at 09:45 +0000, Barry Warsaw wrote:
> It makes sense that if forster crashes, it would leave a stale Mailman
> pidfile laying around. I'll look into this, but the only thing I can
> think of is that the -s flag isn't getting passed to mailmanctl
> properly.
The initscript currently uses "make start" run from the root of the LP
tree.
Also, there are kind of two separate issues here - one is the not using .net/var rather launchpad. net/var) - this means it takes longer for the
the -s flag as above. The other is that the pidfile is in the wrong
directory (/srv/launchpad
than /srv/lists.
LOSA to find it and remove it as it's not in an expected location.