why does MySQL start in runlevel 2 of SuSE? Is there any reason why I cannot have MySQL start in runlevel 3 but ensure it is up before any services
Actually I don't believe the runlevels are messed up at all...simple illustration: for updating your machine you switch to runlevel 2 which gives you the basics of network connectivity but shuts down any server apps and/or user services that may very well need updating. This allows a simple method to take the server offline for updating and when finished you simply switch back to runlevel 3 and all of your programs are restarted. This is a nice little feature. The only concern I had was why did MySQL default to start in RL2 when PostgreSQL, SAPDB default to start in RL3? I thought their may be a significant reason as to why so I thought I would ask. Kevin -----Original Message----- From: Ken Schneider [mailto:kschneider@rtsx.com] Sent: Wednesday, January 15, 2003 10:17 AM To: SuSE Ezine (General) " "(E-mail) Subject: Re: [SLE] Runlevel 2 for MySQL ? There is no reason why you cannot have it start in the run level of your choice. Pardon my rant. It used to be before someone f**ked up the meaning of the run levels that this would not pose a problem. When the system was starting up it would start programs in rc1.d, then rc2.d, then rc3.d (if run level 3 was chosen). And when switching between run levels (2 - 3) you didn't have the problem of a program trying to start again because it would not be listed in rc2.d and rc3.d at the same time. If a program was expected to be running in run level 3 you only need add the entry to rc2.d and it would start as the system was coming UP. A system DOES NOT start in run level 3 it starts at run level 1 and progresses through the run levels until reaching the desired run level. It was a very simple concept at one time. Now you have to make sure you have the program to be run in every run level directory (rc?.d) that you may start the computer at and expect the program to be running when it has finished booting. On Wed, 2003-01-15 at 10:37, Kevin Wilson wrote: that
use it are started?
Thanks. -- Ken Schneider Senior UNIX Administrator Network Administrator kschneider@rtsx.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wed, 2003-01-15 at 12:25, Kevin Wilson wrote:
Actually I don't believe the runlevels are messed up at all...simple illustration:
for updating your machine you switch to runlevel 2 which gives you the basics of network connectivity but shuts down any server apps and/or user services that may very well need updating. This allows a simple method to take the server offline for updating and when finished you simply switch back to runlevel 3 and all of your programs are restarted.
Which was the way that the worked in my unix days. Lets say you normally run the computer in run level 3 (no desktop). There are certain processes that need to start for the computer to function or programs you want running at that run level.. But you also ocassionally start the computer at runlevel 5. You would want the same processes to start in run level 5 so you need to make sure the entrys are in rc5.d as well. Now if you start the computer in runlevel 3 and then decide to go to run level 5 (init 5) it will try to start all of the S* the processes listed in rc5.d even though they are already running. This is were it is f**ked up.
This is a nice little feature. The only concern I had was why did MySQL default to start in RL2 when PostgreSQL, SAPDB default to start in RL3? I thought their may be a significant reason as to why so I thought I would ask.
Kevin
snip -- Ken Schneider Senior UNIX Administrator Network Administrator kschneider@rtsx.com
On Wed, 2003-01-15 at 18:53, Ken Schneider wrote:
Now if you start the computer in runlevel 3 and then decide to go to run level 5 (init 5) it will try to start all of the S* the processes listed in rc5.d even though they are already running.
That's simply not true. The SuSE runlevel script will check if the
S-link exists in the new runlevel, and if so will not run the K-link. It
will not however try to start an already running service. At least not
on my machine. Is there a bug in the rc script on your machine?
--
Anders Johansson
participants (3)
-
Anders Johansson
-
Ken Schneider
-
Kevin Wilson