Mark,
thanks.
> Am 19.10.2016 um 23:55 schrieb Mark Sapiro :
>
> On 10/19/2016 02:51 AM, Matthias Schmidt wrote:
>>
>> Now I get in the system log:
>> com.apple.xpc.launchd[1] (org.mailman): Service only ran for 1 seconds.
>> Pushing respawn out by 9 seconds.
>>
>> and
On 10/19/2016 02:51 AM, Matthias Schmidt wrote:
>
> Now I get in the system log:
> com.apple.xpc.launchd[1] (org.mailman): Service only ran for 1 seconds.
> Pushing respawn out by 9 seconds.
>
> and after that I get:
> The master qrunner lock could not be acquired because it appears as if
Mark,
> Am 19.10.2016 um 13:04 schrieb Mark Sapiro :
>
> On 10/18/2016 07:39 AM, Matthias Schmidt via Mailman-Users wrote:
>>
>> the -s option should fix that problem ;-)
>
>
> If it can determine that the lock is stale.
>
>
>> but if mailman is started as local then -s
On 10/18/2016 07:39 AM, Matthias Schmidt via Mailman-Users wrote:
>
> the -s option should fix that problem ;-)
If it can determine that the lock is stale.
> but if mailman is started as local then -s doesn’t remove a stray pid file.
What do you mean by "if mailman is started as local"?
> Am 18.10.2016 um 22:50 schrieb mailman-admin :
>
> Am 18.10.2016 um 10:57 schrieb Matthias Schmidt via Mailman-Users:
>> Hello,
>> I’m trying to start mailman on startup with ElCapitan.
>>
>> I tried a plist in LaunchDaemons - that was working in the past with
Am 18.10.2016 um 10:57 schrieb Matthias Schmidt via Mailman-Users:
> Hello,
> I’m trying to start mailman on startup with ElCapitan.
>
> I tried a plist in LaunchDaemons - that was working in the past with the
> command:
> /usr/local/mailman/bin/mailmanctl -s start
>
> this produces now the
Hello,
I’m trying to start mailman on startup with ElCapitan.
I tried a plist in LaunchDaemons - that was working in the past with the
command:
/usr/local/mailman/bin/mailmanctl -s start
this produces now the error:
Service only ran for 2 seconds. Pushing respawn out by 8 seconds
the error log