1 |
Michał Górny posted on Fri, 10 Aug 2012 09:43:26 +0200 as excerpted: |
2 |
|
3 |
> On Fri, 10 Aug 2012 05:04:40 +0000 (UTC) |
4 |
> Duncan <1i5t5.duncan@×××.net> wrote: |
5 |
> |
6 |
>> Michał Górny posted on Thu, 09 Aug 2012 22:47:38 +0200 as excerpted: |
7 |
>> |
8 |
>> > Or anything else what can be spawned for shell. And a lot more what |
9 |
>> > you won't expect. And guess what, people are actually doing crazy |
10 |
>> > things with it because someone forgot to tell them how a init.d |
11 |
>> > script should work. |
12 |
>> |
13 |
>> Sounds interesting. A couple quick links to examples of what you had |
14 |
>> in mind would be nice. =:^) |
15 |
|
16 |
> vdr is a first example which comes to my mind. They workaround program |
17 |
> configuration limitations and the init.d scripts become a complex |
18 |
> extra-configuration parser + plugin loader. Well, another thing here is |
19 |
> that upstream AFAIK is not willing to cooperate to fix their config |
20 |
> parsing. |
21 |
> |
22 |
> 'oldnet' is an another example. I'm not saying it should go; I'm saying |
23 |
> it should be a stand-alone executable called from the init.d script. |
24 |
> |
25 |
> Last time I looked, squid init.d was performing post-inst in start(). |
26 |
> Many users may find that beneficial but that's not what init.d scripts |
27 |
> should be doing. |
28 |
|
29 |
Thanks. |
30 |
|
31 |
(As I said my intent wasn't to start a subthread on it, but just to see |
32 |
where you were going with the comment, as it was rather opaque to me as |
33 |
it stood. Oldnet was an especially useful example here given that I run |
34 |
openrc-9999 to more closely follow individual commits, and I've traced |
35 |
and reported a few bugs in oldnet over the years. Now that I know where |
36 |
that comment was going, I'll shutup and contemplate.) |
37 |
|
38 |
-- |
39 |
Duncan - List replies preferred. No HTML msgs. |
40 |
"Every nonfree program has a lord, a master -- |
41 |
and if you use the program, he is your master." Richard Stallman |