On 30-Oct-13 2:49, Dustin C. Hatch wrote:
So how can I fix it on the 1st server, so that syslog-ng starts
after network interface is up?
I would probably fix this by adding
rc_need="net"
to /etc/conf.d/syslog-ng
That's probably cleanest solution. Thanks, it worked like a charm!
The only thin
On 10/29/2013 13:47, Jarry wrote:
Hi Gentoo-users,
I noticed strange message during boot-up of one of my servers:
...
As you see, syslog-ng can not open conection to remote syslog
collector. Reason seems to be quite clear: at the time when
syslog-ng starts, enp3s0 interface is not up (only loopba
On 10/29/2013 10:47 PM, Jarry wrote:
> Hi Gentoo-users,
> I noticed strange message during boot-up of one of my servers:
> __
>
[snip]
>
> As you see, syslog-ng can not open conection to remote syslog
> collector. Reason seems to be quit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/29/13 22:47, Jarry wrote:
> Hi Gentoo-users, I noticed strange message during boot-up of one of
> my servers:
> __
>
> * Bringing up interface lo * 127.0.0.1/8 ...
> [ok] * Adding
Hi Gentoo-users,
I noticed strange message during boot-up of one of my servers:
__
* Bringing up interface lo
* 127.0.0.1/8 ...[ok]
* Adding routes
* 127.0.0.0/8 via 127.0.0.1 ...
5 matches
Mail list logo