Re: Strange /etc/rc.d/netif behaviour
- From: Martin Turgeon <turgeon.martin@xxxxxxxxx>
- Date: Wed, 21 Feb 2007 16:02:12 -0500
John-Mark Gurney a écrit :
Martin Turgeon wrote this message on Wed, Feb 21, 2007 at 11:55 -0500:
I'm not sure if this is really a bug but it doesn't look all fine to me.
When I do a /etc/rc.d/netif restart it does restart the network
interfaces but doesn't replace the default route that it just erased
even if it is specified in rc.conf correctly. I found that I should also
restart routed but it looks strange to me. I know that the /etc/netstart
script did it all but it's written in it that it's obsolete so I don't
want to use it.
So, is this normal and if so what is the best way to restart both a the
same time.
Why don't you restart /etc/rc.d/routing too? That will repopulate the
default route(s) for you..
That is exactly what I did but I would like to know if it is the
expected behaviour and what is the best way to automate this.
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- References:
- Strange /etc/rc.d/netif behaviour
- From: Martin Turgeon
- Re: Strange /etc/rc.d/netif behaviour
- From: John-Mark Gurney
- Strange /etc/rc.d/netif behaviour
- Prev by Date: Re: Strange /etc/rc.d/netif behaviour
- Next by Date: Re: mpd success stories, anyone?
- Previous by thread: Re: Strange /etc/rc.d/netif behaviour
- Next by thread: Re: Strange /etc/rc.d/netif behaviour
- Index(es):
Relevant Pages
|
|
