On Mon, 18 Dec 2006, Jim Crilly wrote:
On 12/18/06 08:18:54PM +0100, Florian Weimer wrote:
* Gabor Gombas:
On Mon, Dec 18, 2006 at 09:23:13AM +0100, Bastian Venthur wrote:
But who has created the allow-hotplug-line? I thought hotplug is dead?
Doesn't matter, udev handles
On Mon, Dec 18, 2006 at 06:36:49PM -0500, Jim Crilly wrote:
I would agree, when I did an install of etch a few weeks ago the use of
allow-hotplug caused the network to come up later in the boot process and
caused problems with syslog-ng remote logging. Apparently when syslog-ng
can't connect
On Tue, Dec 19, 2006 at 11:47:57AM +0100, Peter Palfrader wrote:
I have at least one server machine where allow-hotplug does not reliably
bring up the interface ever.
I had a bug report from a NIS user which turned out to be a result of
them experiencing the same symptoms. They said they
Mark Brown schrieb:
On Tue, Dec 19, 2006 at 11:47:57AM +0100, Peter Palfrader wrote:
I have at least one server machine where allow-hotplug does not reliably
bring up the interface ever.
I had a bug report from a NIS user which turned out to be a result of
them experiencing the same
On 12/19/06 11:52:50AM +0100, Gabor Gombas wrote:
On Mon, Dec 18, 2006 at 06:36:49PM -0500, Jim Crilly wrote:
I would agree, when I did an install of etch a few weeks ago the use of
allow-hotplug caused the network to come up later in the boot process and
caused problems with syslog-ng
Anthony Towns schrieb:
I checked
/etc/network/interfaces on both boxes and noticed the following line:
allow-hotplug eth0
after replacing it with
auto eth0
allow-hotplug interfaces will only be brought up by hotplug (or manually);
you might've deinstall hotplug and replaced it
Hello!
On Mon, 18 Dec 2006 07:36:01 +0100, Anthony Towns wrote:
On Sun, Dec 17, 2006 at 09:58:48PM +0100, Bastian Venthur wrote:
I issued:
# ifup eth0
manually on both boxes but nothing happened.
This probably means that ifup thought the interface was already up
-- ie there was an
On Mon, Dec 18, 2006 at 09:23:13AM +0100, Bastian Venthur wrote:
But who has created the allow-hotplug-line? I thought hotplug is dead?
Doesn't matter, udev handles allow-hotplug interfaces just fine, I use
it on several machines. But the last time I used the Etch installer was
around May...
* Gabor Gombas:
On Mon, Dec 18, 2006 at 09:23:13AM +0100, Bastian Venthur wrote:
But who has created the allow-hotplug-line? I thought hotplug is dead?
Doesn't matter, udev handles allow-hotplug interfaces just fine, I use
it on several machines.
I've seen it quite a few times that udev
On 12/18/06 08:18:54PM +0100, Florian Weimer wrote:
* Gabor Gombas:
On Mon, Dec 18, 2006 at 09:23:13AM +0100, Bastian Venthur wrote:
But who has created the allow-hotplug-line? I thought hotplug is dead?
Doesn't matter, udev handles allow-hotplug interfaces just fine, I use
it on
Hi,
Two or three weeks ago I installed the current latest Debian/Testing on
two different servers. Last week I had to reboot both and noticed that
none of them appeared back in the network again. I checked them locally
and noticed that on both boxes the network interface was not brought up.
I
On Sunday 17 December 2006 13:58, Bastian Venthur wrote:
Two or three weeks ago I installed the current latest Debian/Testing on
two different servers. Last week I had to reboot both and noticed that
none of them appeared back in the network again. I checked them locally
and noticed that on
On Sun, Dec 17, 2006 at 09:58:48PM +0100, Bastian Venthur wrote:
I issued:
# ifup eth0
manually on both boxes but nothing happened.
This probably means that ifup thought the interface was already up --
ie there was an eth0 entry in /etc/network/ifstate. This is supposed to
be cleared on
13 matches
Mail list logo
