From: Roy Dragseth <royd@cc.uit.no>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Re: disabling nics using boot options.
Date: Sun, 12 Jan 2003 19:53:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805667@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805661@msgid-missing>
On Saturday 11 January 2003 01:06, Grant Grundler wrote:
> Roy Dragseth wrote:
> > But, if I put in a sleep 60 after ifup in the /etc/init.d/network
> > script, everything is ok.
>
> IIRC, dhclient forks and lets the child/fork do the actual work.
> With sleep 60, seems the new process would run immediately.
> Perhaps the problem is an issue with the dhclient child-process
> not getting executed before something else attempts to use the
> interface?
Well, as I said in a later mail the problem maninifests itself even if I use
static ip.
> You have time to try "sleep 1" or "sleep 5"
No, I haven't.
>
> > To me, an illiterate when it comes to drivers and network hardware, it
> > seems like the network card (or driver) needs some time to get ready to
> > serve after beeing configured. Again, the problem only occurs when
> > running Gbit, it never shows up when I connect to a 100Mbit switch.
>
> hmmm...I don't know anything about Gbit vs 100Bt negotiations, but maybe
> the Gbit negotiation is just taking longer?
>
Yes, that migth be the case.
r.
--
The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway.
phone:+47 77 64 41 07, fax:+47 77 64 41 00
Roy Dragseth, High Performance Computing System Administrator
Direct call: +47 77 64 62 56. email: royd@cc.uit.no
prev parent reply other threads:[~2003-01-12 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 20:48 [Linux-ia64] Re: Re: disabling nics using boot options Bill Nottingham
2003-01-09 21:23 ` Roy Dragseth
2003-01-10 21:39 ` Roy Dragseth
2003-01-11 0:06 ` Grant Grundler
2003-01-12 19:53 ` Roy Dragseth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590709805667@msgid-missing \
--to=royd@cc.uit.no \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox