Ohai, Chefs!
Can anybody answer my question that is: why is the custom init.d script
created for runit_service instead of just symlinking to “/usr/bin/sv”? This
is about official runit cookbook.
The actual problem is:
I’ve tested the latest runit cookbook on my debian installation and found
out that it just fails in the moment of init.d script creation. I am
already aware of COOK-2322, that corresponds to this problem.
I’ve forked runit cookbook and just removed that code(left only
symlinking). And I can provide it as a pull request. But I do not
completely understand why in the first place this was done before and
uncertain if my fix is appropriate.
P.S. There is also a pull request #17 that fixes the problem in another
way, but it was not mentioned in the ticket. And as far as I understand the
person(ademidov) who provided it is not in the list of approved
contributors(correct me if I’m wrong).
–
Nice day
from Dr. Agon Smith
Hello Dr. Agon,
Good description here - http://tickets.opscode.com/browse/COOK-1576
2013/2/26 Dr. Agon Smith agon.smith@gmail.com
Ohai, Chefs!
Can anybody answer my question that is: why is the custom init.d script
created for runit_service instead of just symlinking to "/usr/bin/sv"? This
is about official runit cookbook.
The actual problem is:
I've tested the latest runit cookbook on my debian installation and found
out that it just fails in the moment of init.d script creation. I am
already aware of COOK-2322, that corresponds to this problem.
I've forked runit cookbook and just removed that code(left only
symlinking). And I can provide it as a pull request. But I do not
completely understand why in the first place this was done before and
uncertain if my fix is appropriate.
P.S. There is also a pull request #17 that fixes the problem in another
way, but it was not mentioned in the ticket. And as far as I understand the
person(ademidov) who provided it is not in the list of approved
contributors(correct me if I'm wrong).
--
Nice day
from Dr. Agon Smith