On Sun, Feb 9, 2014 at 11:35 PM, Daniel Baur <[email protected]> wrote:
> I used the page at [1] to see why corosync throws an error again and
> again. AFAIS the page refers to [2] where a return-code for a not
> running programs is given as 3. So I guess the page [1] is correct,
> isn’t it?

Then the bug appears to be in status_of_proc, which isn't part of the
Lighttpd pkg.


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to