From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: starting and stopping networking
Date: Sun, 04 Jan 2004 14:24:25 -0800 [thread overview]
Message-ID: <5.1.0.14.1.20040104141940.01ed77d8@celine> (raw)
In-Reply-To: <Pine.LNX.4.58.0401041535540.3345@localhost>
At 03:41 PM 1/4/2004 -0600, James Miller wrote:
>On Sun, 4 Jan 2004, James Miller wrote:
>
> > On Sun, 4 Jan 2004 caszonyi@rdslink.ro wrote:
> >
> > > my slack 9.0 has the following lines in /etc/rc.d/rc.inet1 for
> > > bringing up dhcp
> > >
> > > if [ ! "$DHCP_HOSTNAME" = "" ]; then
> > > DHCP_HOSTNAME="-h $DHCP_HOSTNAME"
> > > fi
> > > /sbin/dhcpcd -t 10 ${DHCP_HOSTNAME} -d eth0
> > >
> > > where DHCP_HOSTNAME is the host name of the DHCP server
> > >
> > > Hope it helps a bit :-)
> > >
> > Well, not a whole lot. If I were using Slack, I would just do
> > /etc/rc.d/rc.inet1 stop and /etc/rc.d/rc.inet1 start. I guess I'm trying
> > to find out what is the equivalent on Debian. I'll root through the /etc
> > directory some more and see if I can figure out anything.
> >
>Ok. Taking Jacob's suggestion, I rooted arund in /etc/init.d and found a
>file caled "networking." Looking over its contents, I decided the
>relevant commands for stopping/starting networking on this Debian host are
>"ifdown -a" and "ifup -a", respectively. Just tried it and it seems to
>work. Have I stumbled onto the defnitive solution to my short term
>problem?
One that will serve, at least. Even simpler would be to run (as root, of
course)
/etc/init.d/networking stop
/etc/init.d/networking start
BTW, if you take networking down and later restart it, getting the same
DHCP lease would not be all that amazing ... especially if the DHCP server
assigns long lease lives (the lease itself may still be good, and both your
host and the dhcp server would remember that).
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-01-04 22:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 19:33 disabled system speaker: how to enable? James Miller
2004-01-01 3:33 ` caszonyi
2004-01-01 23:44 ` Debian network reconfigure jamtat
2004-01-01 23:54 ` Ray Olszewski
2004-01-02 0:38 ` James Miller
2004-01-04 20:43 ` starting and stopping networking James Miller
2004-01-04 20:49 ` caszonyi
2004-01-04 21:07 ` James Miller
2004-01-04 21:14 ` Jacob Langley
2004-01-04 21:19 ` caszonyi
2004-01-04 21:28 ` James Miller
2004-01-04 21:41 ` James Miller
2004-01-04 22:24 ` Ray Olszewski [this message]
2004-01-04 21:32 ` Alan Bort
2004-01-04 23:26 ` Ray Olszewski
2004-01-04 23:51 ` Alan Bort
2004-01-05 0:28 ` Ray Olszewski
2004-01-05 3:11 ` Alan Bort
2004-01-05 3:55 ` Juan Facundo Suárez
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=5.1.0.14.1.20040104141940.01ed77d8@celine \
--to=ray@comarre.com \
--cc=linux-newbie@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