Erwan David wrote:
> Everything in /etc/networkinterfaces.
>
> It is a bit complicated let me explain the situation before going to
> configuration:
Actually your situation sounds pretty normal to me.
> # The primary network interface
> auto eth0
> iface eth0 inet static
> address 88.190.17.
On Wed, Dec 11, 2013 at 07:02:14PM CET, Bob Proulx said:
>
> In that case we will need to keep peeling back layers until the root
> cause is found. How are you starting the network? Is this a section
> listed in /etc/network/interfaces? Please show us the section. Or is
> this using NetworkM
Erwan David wrote:
> Bob Proulx said:
> > Erwan David wrote:
> > > I have a problem that services are started on a server I manage before
> > > link is UP. This leads to some services failing, or not bound to every
> > > addresses :
> >
> > Please say what release track you are using? Unstable, T
On Wed, Dec 11, 2013 at 12:12:14AM CET, Bob Proulx said:
> Erwan David wrote:
> > I have a problem that services are started on a server I manage before
> > link is UP. This leads to some services failing, or not bound to every
> > addresses :
>
> Please say what release track you are using? Uns
Erwan David wrote:
> I have a problem that services are started on a server I manage before
> link is UP. This leads to some services failing, or not bound to every
> addresses :
Please say what release track you are using? Unstable, Testing, Stable?
Please say whether you are using parallel boo
I have a problem that services are started on a server I manage before
link is UP. This leads to some services failing, or not bound to every
addresses :
here is an excerpt from the logs :
Dec 10 18:21:24 tee acpid: starting up with netlink and the input layer
Dec 10 18:21:24 tee acpid: 1 rule lo
6 matches
Mail list logo
