On Thu, 24 Oct 2002, Craig wrote:
> Hi folks,
> I'm using the new Bering 1.04, and I'm sorry for posting this (because
> I'm sure it's been asked before)...how to you "restart" Bering once
> you've made changes (and then backed them up) without rebooting? Thank
> you.
You don't "restart Bering" without rebooting it.
Bering is a collection of different functional subsystems, from the kernel
to the shell, weblet, ssh daemon, and lots of others as well. To "restart
Bering" you pretty much imply you are restarting all of these... which
is a reboot.
You do have a limited form of standardized control over many of these
individual subsystems, though, through the various shell scripts in
/etc/init.d. These scripts often use the configuration information you
have edited in files in /etc to direct their operation.
These scripts are generically written to start, stop, and restart the
subsystems they control based on conventional arguments. Try looking
through some of these scripts at a big picture level... they almost always
have a case statement that directs their operation (the ones that don't
are typically only executed once on startup and never again). If you know
which subsystem needs to be restarted, for example, you just need to know
the name of the script that controls that subsystem, and the appropriate
generic argument to do what you want (start, stop, restart are the most
common).
So, if you have edited /etc/network/interfaces, you probably want to
invoke "/etc/init.d/networking restart", and probably also want to do
"shorewall restart" because the firewall depends on the networking
configuration.
A shortcut to execute any of those scripts from any directory without
tacking on the /etc/init.d/ is the "svi" alias:
svi networking restart
Sometimes the subsystems depend on each other... you pretty much have to
learn which ones depend on which others by experience... you can get an
idea by looking at the sort order for the "Snn" symbolic links in
/etc/rcS.d and /etc/rc2.d that are derived from the RCDLINKS variables in
the startups scripts in /etc/init.d. If they have the same "nn" then they
are probably independent. If one depends on another, the dependent one
will have a larger value of "nn" than the one it depends on. (Different
"nn" values doesn't automatically imply dependence, though.)
If you don't know these dependencies, you may find it more predictable to
reboot the router to insure that all scripts are executed in
order. However, by experimenting and reading scripts, you can save
yourself time by restarting the appropriate subsystems.
---------------------------------------------------------------------------
Jeff Newmiller The ..... ..... Go Live...
DCN:<[EMAIL PROTECTED]> Basics: ##.#. ##.#. Live Go...
Live: OO#.. Dead: OO#.. Playing
Research Engineer (Solar/Batteries O.O#. #.O#. with
/Software/Embedded Controllers) .OO#. .OO#. rocks...2k
---------------------------------------------------------------------------
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
