| 1 |
On Tue, 23 Nov 2004, Konstantin V. Gavrilenko wrote: |
| 2 |
|
| 3 |
> Guys, |
| 4 |
> |
| 5 |
> just thought I should mention this. |
| 6 |
> |
| 7 |
> if you setup a syslog-ng server that binds to an interface and listens |
| 8 |
> to collect incoming logs, at the next reboot it will fail to do so. I |
| 9 |
> believe this issue is due to the order of execution of the init.d |
| 10 |
> initialization scripts, since syslog-ng is started before the net.ethX |
| 11 |
> scripts are executed. The exim would not start following the failure |
| 12 |
> of the syslog-ng. |
| 13 |
|
| 14 |
My experience is, this is actually unpredictable - net.ethX does not |
| 15 |
provide 'net', and so whether syslog-ng (or, for that matter, any other |
| 16 |
syslog service) starts up before or after the network is established is |
| 17 |
anyone's guess. Given the total number of places it can start up on a |
| 18 |
typical system, I would guess that it probably usually starts after the |
| 19 |
network has initialized. |
| 20 |
|
| 21 |
Further, iptables needs 'logger', but must start before net, although it |
| 22 |
works fine for me to start it before syslog-ng. (I don't know that |
| 23 |
'need' indicates an order. But before I removed that need from my own |
| 24 |
iptables init script, iptables was always running after syslog-ng (and, |
| 25 |
incidentally, a minute or two after my network came up. I'm glad I have |
| 26 |
multiple layers of defenses, and Linux isn't the prime target.)) |
| 27 |
|
| 28 |
My submitted work thus far in documenting this bug: |
| 29 |
|
| 30 |
http://bugs.gentoo.org/show_bug.cgi?id=70226 |
| 31 |
|
| 32 |
|
| 33 |
I apologize for the lack of proper line wraps in that post; it appears |
| 34 |
bugzilla and my browser do not agree. (IMHO, if a text area is to not |
| 35 |
auto-wrap, it should have both horizontal and vertical scroll-bars. My |
| 36 |
browser agrees with this.) |
| 37 |
|
| 38 |
Ed |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives