FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 07-07-2011, 09:33 PM
Wayne Topa
 
Default Restarting network

On 07/07/2011 04:02 PM, William Hopkins wrote:
> On 07/07/11 at 11:26am, Wayne Topa wrote:
>> On 07/07/2011 10:42 AM, Tony van der Hoff wrote:
>>> Having made some config changes to my network, I did:
>>>
>>> root@tony-lx:/home/tony# /etc/init.d/networking restart
>>>
>>> That results in:
>>>
>>> Running /etc/init.d/networking restart is deprecated because it may not
>>> enable again some interfaces ... (warning).
>>> Reconfiguring network interfaces...
>>>
>>> OK, so it's deprecated. What should I use instead??
>>>
>>
>> Um how about in wheezy or sid
>> service networking stop ; service networking start
>
> Always use && and not ';'; otherwise you may run start after an unsuccessful
> stop.
>
True and I should have said that. Thanks Liam


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E162618.4060605@gmail.com">http://lists.debian.org/4E162618.4060605@gmail.com
 
Old 07-07-2011, 09:46 PM
Brian
 
Default Restarting network

On Thu 07 Jul 2011 at 20:45:54 +0100, Joe wrote:

> But presumably at boot, all interfaces, whether auto or not, are
> successfully started, and presumably properly closed down on shutdown.

When booting, interfaces marked 'auto' are brought up by scripts in
/etc/init.d. However, interfaces marked 'allow-hotplug' are brought up
by scripts run by udev. The end result is (or should be) the same but
the mechanisms are different.

Interfaces marked with neither are not activated.

> Is there no command-line access to whatever mechanism does this? Do we
> really need to keep a list of current interface names on a sticky
> note on the monitor and ifup them individually?

ifup/ifdown will always do what their names imply. You would need to
have knowledge of the interfaces on your machine to use the commands. A
sticky-note might help.

The point which the OP raised was the purpose of /etc/init.d/networking
(or perhaps, like me, he was puzzled by the use of the word
'deprecated). It sounds as though it will enable all interfaces. It
doesn't, unless they are marked 'auto',

So - some lateral thinking. Mark every interface (apart from lo) auto
*and* 'allow-hotplug'. '/etc/init.d/networking restart' or
'/etc/init.d/networking start' would now work. Does that address your
query?

There are two schools of thought about this. One is that it is bad, the
other is that it is ok.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110707214641.GC15615@desktop">http://lists.debian.org/20110707214641.GC15615@desktop
 
Old 07-08-2011, 12:43 AM
shawn wilson
 
Default Restarting network

On Jul 7, 2011 4:02 PM, "William Hopkins" <we.hopkins@gmail.com> wrote:

>

> On 07/07/11 at 11:26am, Wayne Topa wrote:

> > On 07/07/2011 10:42 AM, Tony van der Hoff wrote:


> >

> > Um how about in wheezy or sid

> > service networking stop ; service networking start

>

> Always use && and not ';'; otherwise you may run start after an unsuccessful

> stop.

>


Awe, come now, live dangerous. I used to build kernels with:

make; make modules; make modules_install; make bzImage; make bzlilo


It's been a while so I probably got a few things off (and no initfs). But you get the idea. Oh and I once did a make -ik (IIRC) on a dev kernel but the linker failed


Either way, I'm generally remote when doing this stuff. So, if networking isn't brought completely down, I still want it to try to come back up.
 
Old 07-08-2011, 08:46 AM
Joe
 
Default Restarting network

On Thu, 7 Jul 2011 22:46:41 +0100
Brian <ad44@cityscape.co.uk> wrote:

>
> ifup/ifdown will always do what their names imply. You would need to
> have knowledge of the interfaces on your machine to use the commands.
> A sticky-note might help.
>
>
> So - some lateral thinking. Mark every interface (apart from lo) auto
> *and* 'allow-hotplug'. '/etc/init.d/networking restart' or
> '/etc/init.d/networking start' would now work. Does that address your
> query?
>
> There are two schools of thought about this. One is that it is bad,
> the other is that it is ok.
>
>
Thank you, I knew some of this and since I haven't needed a networking
restart for some time, probably over a year, I haven't needed to
investigate in detail. But I've needed to do it several times in the
past, and probably will again.

The issue will only arise with something complicated i.e. a server.
Mine has two Ethernet NICs with static addresses, plus a changing
assortment of VM and VPN endpoints, which of course aren't listed in
interfaces. I have a feeling that if I do something drastic enough to
need a networking restart, I'll now need to reboot to be sure.

--
Joe


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110708094650.6c2f40e8@jresid.jretrading.com">htt p://lists.debian.org/20110708094650.6c2f40e8@jresid.jretrading.com
 
Old 07-08-2011, 09:47 AM
Erwan David
 
Default Restarting network

Le Thu 7/07/2011, Brian disait
> On Thu 07 Jul 2011 at 20:45:54 +0100, Joe wrote:
>
> > But presumably at boot, all interfaces, whether auto or not, are
> > successfully started, and presumably properly closed down on shutdown.
>
> When booting, interfaces marked 'auto' are brought up by scripts in
> /etc/init.d. However, interfaces marked 'allow-hotplug' are brought up
> by scripts run by udev. The end result is (or should be) the same but
> the mechanisms are different.
>
> Interfaces marked with neither are not activated.
>
> > Is there no command-line access to whatever mechanism does this? Do we
> > really need to keep a list of current interface names on a sticky
> > note on the monitor and ifup them individually?
>
> ifup/ifdown will always do what their names imply. You would need to
> have knowledge of the interfaces on your machine to use the commands. A
> sticky-note might help.
>
> The point which the OP raised was the purpose of /etc/init.d/networking
> (or perhaps, like me, he was puzzled by the use of the word
> 'deprecated). It sounds as though it will enable all interfaces. It
> doesn't, unless they are marked 'auto',
>
> So - some lateral thinking. Mark every interface (apart from lo) auto
> *and* 'allow-hotplug'. '/etc/init.d/networking restart' or
> '/etc/init.d/networking start' would now work. Does that address your
> query?
>
> There are two schools of thought about this. One is that it is bad, the
> other is that it is ok.

Allow-hotplug could be interesting for a removable NIC (PCMCIA, expresscard etc.) But what is the use for a fixed NIC ?

--
Erwan


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110708094746.GA5781@rail.eu.org">http://lists.debian.org/20110708094746.GA5781@rail.eu.org
 
Old 07-08-2011, 09:51 AM
Tony van der Hoff
 
Default Restarting network

On 07/07/11 22:46, Brian wrote:

On Thu 07 Jul 2011 at 20:45:54 +0100, Joe wrote:


But presumably at boot, all interfaces, whether auto or not, are
successfully started, and presumably properly closed down on shutdown.


When booting, interfaces marked 'auto' are brought up by scripts in
/etc/init.d. However, interfaces marked 'allow-hotplug' are brought up
by scripts run by udev. The end result is (or should be) the same but
the mechanisms are different.

Interfaces marked with neither are not activated.


Is there no command-line access to whatever mechanism does this? Do we
really need to keep a list of current interface names on a sticky
note on the monitor and ifup them individually?


ifup/ifdown will always do what their names imply. You would need to
have knowledge of the interfaces on your machine to use the commands. A
sticky-note might help.

The point which the OP raised was the purpose of /etc/init.d/networking
(or perhaps, like me, he was puzzled by the use of the word
'deprecated). It sounds as though it will enable all interfaces. It
doesn't, unless they are marked 'auto',

So - some lateral thinking. Mark every interface (apart from lo) auto
*and* 'allow-hotplug'. '/etc/init.d/networking restart' or
'/etc/init.d/networking start' would now work. Does that address your
query?

There are two schools of thought about this. One is that it is bad, the
other is that it is ok.



I'm the OP.
Thanks, all, for your help and advice.

Being able to issue a 'restart' on a service has become the de facto way
of indicating a configuration change. I would have thought that the
devs, instead of just issuing a warning, could have worked round the
problem. Maybe it's on someone's todo list.


It looks to me, that as I have a simple network, with a single
interface, I'd be quite safe in ignoring the warning.


Cheers, Tony
--
Tony van der Hoff | mailto:tony@vanderhoff.org
Buckinghamshire, England |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4E16D31E.1010909@vanderhoff.org">http://lists.debian.org/4E16D31E.1010909@vanderhoff.org
 
Old 07-08-2011, 06:25 PM
Brian
 
Default Restarting network

On Fri 08 Jul 2011 at 11:47:46 +0200, Erwan David wrote:

> Allow-hotplug could be interesting for a removable NIC (PCMCIA,
> expresscard etc.) But what is the use for a fixed NIC ?

Booting is quicker with DHCP (especially if dhclient times out) than
with auto.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110708182559.GD15615@desktop">http://lists.debian.org/20110708182559.GD15615@desktop


Fri Jul 8 22:30:07 2011
Return-path: <bounce-debian-devel=tom=linux-archive.org@lists.debian.org>
Envelope-to: tom@linux-archive.org
Delivery-date: Fri, 08 Jul 2011 21:38:23 +0300
Received: from liszt.debian.org ([82.195.75.100]:59064)
by s2.java-tips.org with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.69)
(envelope-from <bounce-debian-devel=tom=linux-archive.org@lists.debian.org>)
id 1QfFwT-0008VU-5m
for tom@linux-archive.org; Fri, 08 Jul 2011 21:38:22 +0300
Received: from localhost (localhost [127.0.0.1])
by liszt.debian.org (Postfix) with QMQP
id 7D1F313A52B1; Fri, 8 Jul 2011 18:42:16 +0000 (UTC)
Old-Return-Path: <debbugs@busoni.debian.org>
X-Original-To: lists-debian-devel@liszt.debian.org
Delivered-To: lists-debian-devel@liszt.debian.org
Received: from localhost (localhost [127.0.0.1])
by liszt.debian.org (Postfix) with ESMTP id 366CB13A5139
for <lists-debian-devel@liszt.debian.org>; Fri, 8 Jul 2011 18:42:16 +0000 (UTC)
X-Virus-Scanned: at lists.debian.org with policy bank en-ht
X-Spam-Flag: NO
X-Spam-Score: -9.5
X-Spam-Level:
X-Spam-Status: No, score=-9.5 tagged_above=-10000 required=5.3
tests=[BAYES_00=-2, BODY_8BITS=1.5, LDO_WHITELIST=-5,
RCVD_IN_DNSWL_MED=-4] autolearn=ham
Received: from liszt.debian.org ([127.0.0.1])
by localhost (lists.debian.org [127.0.0.1]) (amavisd-new, port 2525)
with ESMTP id XZ8-oQTmjMHC for <lists-debian-devel@liszt.debian.org>;
Fri, 8 Jul 2011 18:42:08 +0000 (UTC)
Received: from busoni.debian.org (busoni.debian.org [140.211.15.34])
(using TLSv1 with cipher AES256-SHA (256/256 bits))
(Client did not present a certificate)
by liszt.debian.org (Postfix) with ESMTPS id 8803E13A4A16;
Fri, 8 Jul 2011 18:42:08 +0000 (UTC)
Received: from debbugs by busoni.debian.org with local (Exim 4.72)
(envelope-from <debbugs@busoni.debian.org>)
id 1QfG04-0006Hu-C7; Fri, 08 Jul 2011 18:42:04 +0000
X-Loop: owner@bugs.debian.org
Subject: Bug#633131: ITP: diod -- I/O forwarding server for 9P
Reply-To: =?UTF-8?Q?=D0=84=D0=B2=D0=B3=D0=B5=D0=BD=D1=96=D0=B9_?= =?UTF-8?Q?=D0=9C=D0=B5=D1=89=D0=B5=D1=80=D1=8F=D0=BA=D0= BE=D0=B2?= <eugen@debian.org>, 633131@bugs.debian.org
Resent-From: =?UTF-8?Q?=D0=84=D0=B2=D0=B3=D0=B5=D0=BD=D1=96=D0=B9_?= =?UTF-8?Q?=D0=9C=D0=B5=D1=89=D0=B5=D1=80=D1=8F=D0=BA=D0= BE=D0=B2?= <eugen@debian.org>
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: debian-devel@lists.debian.org, wnpp@debian.org, "=?UTF-8?Q?=D0=84=D0=B2=D0=B3=D0=B5=D0=BD=D1=96=D0=B9_?= =?UTF-8?Q?=D0=9C=D0=B5=D1=89=D0=B5=D1=80=D1=8F=D0=BA=D0= BE=D0=B2?=" <eugen@debian.org>
X-Loop: owner@bugs.debian.org
Resent-Date: Fri, 08 Jul 2011 18:42:01 +0000
Resent-Message-ID: <handler.633131.B.131015032723362@bugs.debian.or g>
X-Debian-PR-Message: report 633131
X-Debian-PR-Package: wnpp
X-Debian-PR-Keywords:
Received: via spool by submit@bugs.debian.org id=B.131015032723362
(code B ref -1); Fri, 08 Jul 2011 18:42:01 +0000
Received: (at submit) by bugs.debian.org; 8 Jul 2011 18:38:47 +0000
X-Spam-Bayes: score:0.0000 Tokens: new, 8; hammy, 116; neutral, 37; spammy, 1.
spammytokens:0.993-1--diod hammytokens:0.000-+--H*M:reportbug,
0.000-+--H*MI:reportbug, 0.000-+--H*x:reportbug, 0.000-+--H*UA:reportbug,
0.000-+--HX-Debbugs-Cc:sk:debian-
Received: from smtp2.tu-cottbus.de ([141.43.99.248])
by busoni.debian.org with esmtps (TLS1.0HE_RSA_AES_256_CBC_SHA1:32)
(Exim 4.72)
(envelope-from <eugen@debian.org>)
id 1QfFws-00064P-QI
for submit@bugs.debian.org; Fri, 08 Jul 2011 18:38:47 +0000
Received: from localhost (localhost [127.0.0.1])
by smtp2.tu-cottbus.de (Postfix) with ESMTP id 3212169018C;
Fri, 8 Jul 2011 20:38:38 +0200 (CEST)
X-Virus-Scanned: by AMaViS (at smtp2.tu-cottbus.de)
Received: from loki (cd1.cd.tu-cottbus.de [141.43.159.77])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
(Authenticated sender: meshciev)
by smtp2.tu-cottbus.de (Postfix) with ESMTPSA id 6C2D5690188;
Fri, 8 Jul 2011 20:38:33 +0200 (CEST)
Received: by loki (Postfix, from userid 1000)
id 8469C110ED5; Fri, 8 Jul 2011 20:40:11 +0200 (CEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
From: =?UTF-8?Q?=D0=84=D0=B2=D0=B3=D0=B5=D0=BD=D1=96=D0=B9_?= =?UTF-8?Q?=D0=9C=D0=B5=D1=89=D0=B5=D1=80=D1=8F=D0=BA=D0= BE=D0=B2?=
<eugen@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Message-ID: <20110708184011.17248.45159.reportbug@localhost>
X-Mailer: reportbug 5.1.1
Date: Fri, 08 Jul 2011 20:40:11 +0200
Content-Transfer-Encoding: quoted-printable
Delivered-To: submit@bugs.debian.org
X-Rc-Virus: 2007-09-13_01
X-Mailing-List: <debian-devel@lists.debian.org> archive/latest/273731
X-Loop: debian-devel@lists.debian.org
List-Id: <debian-devel.lists.debian.org>
List-Post: <mailto:debian-devel@lists.debian.org>
List-Help: <mailto:debian-devel-request@lists.debian.org?subject=help>
List-Subscribe: <mailto:debian-devel-request@lists.debian.org?subject=subscribe>
List-Unsubscribe: <mailto:debian-devel-request@lists.debian.org?subject=unsubscribe>
Precedence: list
Resent-Sender: debian-devel-request@lists.debian.org

Package: wnpp
Severity: wishlist
Owner: "=D0=84=D0=B2=D0=B3=D0=B5=D0=BD=D1=96=D0=B9 =D0=9C=D0=B5=D1=89=D0=B5=
=D1=80=D1=8F=D0=BA=D0=BE=D0=B2" <eugen@debian.org>

* Package name : diod
Version : 1.0~pre44
Upstream Author : Jim Garlick garlick at llnl dot gov
* URL : http://code.google.com/p/diod/
* License : GPL, BSD
Programming Lang: C
Description : I/O forwarding server for 9P

diod is a 9P server used in combination with the kernel v9fs file
system for I/O forwarding on Linux clusters.



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20110708184011.17248.45159.reportbug@localhost
 
Old 07-08-2011, 06:25 PM
Brian
 
Default Restarting network

On Fri 08 Jul 2011 at 11:47:46 +0200, Erwan David wrote:

> Allow-hotplug could be interesting for a removable NIC (PCMCIA,
> expresscard etc.) But what is the use for a fixed NIC ?

Booting is quicker with DHCP (especially if dhclient times out) than
with auto.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110708182559.GD15615@desktop">http://lists.debian.org/20110708182559.GD15615@desktop


Fri Jul 8 22:30:07 2011
Return-path: <bounce-debian-devel=tom=linux-archive.org@lists.debian.org>
Envelope-to: tom@linux-archive.org
Delivery-date: Fri, 08 Jul 2011 21:38:23 +0300
Received: from liszt.debian.org ([82.195.75.100]:59064)
by s2.java-tips.org with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.69)
(envelope-from <bounce-debian-devel=tom=linux-archive.org@lists.debian.org>)
id 1QfFwT-0008VU-5m
for tom@linux-archive.org; Fri, 08 Jul 2011 21:38:22 +0300
Received: from localhost (localhost [127.0.0.1])
by liszt.debian.org (Postfix) with QMQP
id 7D1F313A52B1; Fri, 8 Jul 2011 18:42:16 +0000 (UTC)
Old-Return-Path: <debbugs@busoni.debian.org>
X-Original-To: lists-debian-devel@liszt.debian.org
Delivered-To: lists-debian-devel@liszt.debian.org
Received: from localhost (localhost [127.0.0.1])
by liszt.debian.org (Postfix) with ESMTP id 366CB13A5139
for <lists-debian-devel@liszt.debian.org>; Fri, 8 Jul 2011 18:42:16 +0000 (UTC)
X-Virus-Scanned: at lists.debian.org with policy bank en-ht
X-Spam-Flag: NO
X-Spam-Score: -9.5
X-Spam-Level:
X-Spam-Status: No, score=-9.5 tagged_above=-10000 required=5.3
tests=[BAYES_00=-2, BODY_8BITS=1.5, LDO_WHITELIST=-5,
RCVD_IN_DNSWL_MED=-4] autolearn=ham
Received: from liszt.debian.org ([127.0.0.1])
by localhost (lists.debian.org [127.0.0.1]) (amavisd-new, port 2525)
with ESMTP id XZ8-oQTmjMHC for <lists-debian-devel@liszt.debian.org>;
Fri, 8 Jul 2011 18:42:08 +0000 (UTC)
Received: from busoni.debian.org (busoni.debian.org [140.211.15.34])
(using TLSv1 with cipher AES256-SHA (256/256 bits))
(Client did not present a certificate)
by liszt.debian.org (Postfix) with ESMTPS id 8803E13A4A16;
Fri, 8 Jul 2011 18:42:08 +0000 (UTC)
Received: from debbugs by busoni.debian.org with local (Exim 4.72)
(envelope-from <debbugs@busoni.debian.org>)
id 1QfG04-0006Hu-C7; Fri, 08 Jul 2011 18:42:04 +0000
X-Loop: owner@bugs.debian.org
Subject: Bug#633131: ITP: diod -- I/O forwarding server for 9P
Reply-To: =?UTF-8?Q?=D0=84=D0=B2=D0=B3=D0=B5=D0=BD=D1=96=D0=B9_?= =?UTF-8?Q?=D0=9C=D0=B5=D1=89=D0=B5=D1=80=D1=8F=D0=BA=D0= BE=D0=B2?= <eugen@debian.org>, 633131@bugs.debian.org
Resent-From: =?UTF-8?Q?=D0=84=D0=B2=D0=B3=D0=B5=D0=BD=D1=96=D0=B9_?= =?UTF-8?Q?=D0=9C=D0=B5=D1=89=D0=B5=D1=80=D1=8F=D0=BA=D0= BE=D0=B2?= <eugen@debian.org>
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: debian-devel@lists.debian.org, wnpp@debian.org, "=?UTF-8?Q?=D0=84=D0=B2=D0=B3=D0=B5=D0=BD=D1=96=D0=B9_?= =?UTF-8?Q?=D0=9C=D0=B5=D1=89=D0=B5=D1=80=D1=8F=D0=BA=D0= BE=D0=B2?=" <eugen@debian.org>
X-Loop: owner@bugs.debian.org
Resent-Date: Fri, 08 Jul 2011 18:42:01 +0000
Resent-Message-ID: <handler.633131.B.131015032723362@bugs.debian.or g>
X-Debian-PR-Message: report 633131
X-Debian-PR-Package: wnpp
X-Debian-PR-Keywords:
Received: via spool by submit@bugs.debian.org id=B.131015032723362
(code B ref -1); Fri, 08 Jul 2011 18:42:01 +0000
Received: (at submit) by bugs.debian.org; 8 Jul 2011 18:38:47 +0000
X-Spam-Bayes: score:0.0000 Tokens: new, 8; hammy, 116; neutral, 37; spammy, 1.
spammytokens:0.993-1--diod hammytokens:0.000-+--H*M:reportbug,
0.000-+--H*MI:reportbug, 0.000-+--H*x:reportbug, 0.000-+--H*UA:reportbug,
0.000-+--HX-Debbugs-Cc:sk:debian-
Received: from smtp2.tu-cottbus.de ([141.43.99.248])
by busoni.debian.org with esmtps (TLS1.0HE_RSA_AES_256_CBC_SHA1:32)
(Exim 4.72)
(envelope-from <eugen@debian.org>)
id 1QfFws-00064P-QI
for submit@bugs.debian.org; Fri, 08 Jul 2011 18:38:47 +0000
Received: from localhost (localhost [127.0.0.1])
by smtp2.tu-cottbus.de (Postfix) with ESMTP id 3212169018C;
Fri, 8 Jul 2011 20:38:38 +0200 (CEST)
X-Virus-Scanned: by AMaViS (at smtp2.tu-cottbus.de)
Received: from loki (cd1.cd.tu-cottbus.de [141.43.159.77])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
(Authenticated sender: meshciev)
by smtp2.tu-cottbus.de (Postfix) with ESMTPSA id 6C2D5690188;
Fri, 8 Jul 2011 20:38:33 +0200 (CEST)
Received: by loki (Postfix, from userid 1000)
id 8469C110ED5; Fri, 8 Jul 2011 20:40:11 +0200 (CEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
From: =?UTF-8?Q?=D0=84=D0=B2=D0=B3=D0=B5=D0=BD=D1=96=D0=B9_?= =?UTF-8?Q?=D0=9C=D0=B5=D1=89=D0=B5=D1=80=D1=8F=D0=BA=D0= BE=D0=B2?=
<eugen@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Message-ID: <20110708184011.17248.45159.reportbug@localhost>
X-Mailer: reportbug 5.1.1
Date: Fri, 08 Jul 2011 20:40:11 +0200
Content-Transfer-Encoding: quoted-printable
Delivered-To: submit@bugs.debian.org
X-Rc-Virus: 2007-09-13_01
X-Mailing-List: <debian-devel@lists.debian.org> archive/latest/273731
X-Loop: debian-devel@lists.debian.org
List-Id: <debian-devel.lists.debian.org>
List-Post: <mailto:debian-devel@lists.debian.org>
List-Help: <mailto:debian-devel-request@lists.debian.org?subject=help>
List-Subscribe: <mailto:debian-devel-request@lists.debian.org?subject=subscribe>
List-Unsubscribe: <mailto:debian-devel-request@lists.debian.org?subject=unsubscribe>
Precedence: list
Resent-Sender: debian-devel-request@lists.debian.org

Package: wnpp
Severity: wishlist
Owner: "=D0=84=D0=B2=D0=B3=D0=B5=D0=BD=D1=96=D0=B9 =D0=9C=D0=B5=D1=89=D0=B5=
=D1=80=D1=8F=D0=BA=D0=BE=D0=B2" <eugen@debian.org>

* Package name : diod
Version : 1.0~pre44
Upstream Author : Jim Garlick garlick at llnl dot gov
* URL : http://code.google.com/p/diod/
* License : GPL, BSD
Programming Lang: C
Description : I/O forwarding server for 9P

diod is a 9P server used in combination with the kernel v9fs file
system for I/O forwarding on Linux clusters.



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20110708184011.17248.45159.reportbug@localhost
 
Old 07-09-2011, 09:20 AM
Andrei POPESCU
 
Default Restarting network

On Vi, 08 iul 11, 19:25:59, Brian wrote:
> On Fri 08 Jul 2011 at 11:47:46 +0200, Erwan David wrote:
>
> > Allow-hotplug could be interesting for a removable NIC (PCMCIA,
> > expresscard etc.) But what is the use for a fixed NIC ?
>
> Booting is quicker with DHCP (especially if dhclient times out) than
> with auto.

Could you please expand on this? I don't understand what you mean.

Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
 
Old 07-09-2011, 03:29 PM
Brian
 
Default Restarting network

On Sat 09 Jul 2011 at 12:20:36 +0300, Andrei POPESCU wrote:

> On Vi, 08 iul 11, 19:25:59, Brian wrote:
> >
> > Booting is quicker with DHCP (especially if dhclient times out) than
> > with auto.
>
> Could you please expand on this? I don't understand what you mean.

As a matter of observation I notice the booting process pauses when
/e/n/i uses

auto etho
iface eth0 inet dhcp

It may only be for 2 or 3 seconds while dhclient does what it has to do
and outputs its actions to the screen, but it can be longer. Without a
network cable attached there is a 60 second delay before booting
continues.

Substitute 'allow-hotplug' for 'auto' and there is no pausing at all and
dhclient gets on with its job in the background.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110709152955.GG15615@desktop">http://lists.debian.org/20110709152955.GG15615@desktop
 

Thread Tools




All times are GMT. The time now is 07:29 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org