Hello Stephen,
I had earlier contacted you on the developer
mailing list regarding the gsoc project.
I have started reading about ARC as you suggested and have thought
about a few things.
When we use mailman, the mailing list service adds an extra phrase in
the subject - [Mailman-Developers] and an
And I had previously mailed you directly, but I think I missed you
there. So I mailed it again here.
Sorry if I caused any inconvenience.
On Mon, Feb 8, 2016 at 2:26 PM, Aditya Divekar
wrote:
> Hello Stephen,
> I had earlier contacted you on the developer
> mailing list regarding the gsoc project
I got the following error when I was trying to start the mailman service today -
master: error: The master lock could not be acquired. It appears as
though there is a stale master lock
It first printed a long script regarding the Master subprocess watcher
and then threw the above error.
It was
On 02/08/2016 08:42 AM, Aditya Divekar wrote:
> I got the following error when I was trying to start the mailman service
> today -
>
> master: error: The master lock could not be acquired. It appears as
> though there is a stale master lock
The service was not gracefully stopped the last time
Aditya Divekar writes:
> And I had previously mailed you directly, but I think I missed you
> there. So I mailed it again here.
No, I've just been really busy with work, and a very bad cold,
sleeping about 2 hours/day more than usual. I'll get back to you
tomorrow evening my time (it's 2am her
@ Abhilash Raj - Thanks for your swift reply. It worked. I terminated
it wrongly last time I suppose.
@ Mark Sapiro - Yes, there was a stale lock file not associated with
any process. Removed it. And I'll go through the FAQ. Thanks!
On Mon, Feb 8, 2016 at 10:40 PM, Mark Sapiro wrote:
> On 02/0
