1 |
A few responses: |
2 |
(Please forgive the lack of normal formatting) |
3 |
|
4 |
1) To Chris Gianelloni |
5 |
|
6 |
I really do agree that it's silly for a daemon to lie about it's |
7 |
initialization status. However, after actually haven taken some of |
8 |
these issues upstream (in particular Apache 1.3). I realized that the |
9 |
upstream devs don't really consider these bugs all of the time. In |
10 |
Apache's case, it's a bug, but one that's never going to be fixed in 1.3 |
11 |
(2.0 supposedly fixes it). I think there was one case where pure-ftpd |
12 |
actually fixed one of these bugs when I reported it. |
13 |
|
14 |
My point is that Snort and Apache are not alone in this, so I suppose |
15 |
quite a few upstream developers just disagree with us on what proper |
16 |
initialization means. Why should our users suffer? |
17 |
|
18 |
|
19 |
2) To Mike Frysinger |
20 |
|
21 |
Most of these services are pretty common, and the suckage is usually |
22 |
limited to this area of initialization =) |
23 |
|
24 |
I do see how timing could be an issue for sleeps, but I would personally |
25 |
much rather have a timeout variable in conf.d somewhere rather than no |
26 |
check at all. |
27 |
|
28 |
I would also much rather have a simple check be performed that produced |
29 |
false positives itself (which is what the init scripts are doing now), |
30 |
as long as it cut down on the total number of false positives. |
31 |
|
32 |
|
33 |
3) To anyone else |
34 |
|
35 |
So far it looks like developer awareness is the best we can do? |
36 |
What about making standard functions or check services available to help |
37 |
developers who are aware and need to use them? |
38 |
|
39 |
Even if developers just become willing to add checks, that would be |
40 |
great. Right now most devs simply rely on upstream (although I think |
41 |
upstream should certainly be a part of each case). |
42 |
|
43 |
-- |
44 |
gentoo-dev@g.o mailing list |