Re: Too Slow To Stop

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8/7/07, Mikkel L. Ellertson <mikkel@xxxxxxxxxxxxxxxx> wrote:
> Kam Leo wrote:
> > On 8/7/07, Mikkel L. Ellertson <mikkel@xxxxxxxxxxxxxxxx> wrote:
> >> Konstantin Svist wrote:
> >>> Actually 90 is the indicator of when it will be stopped
> >>> with sysVinit, all services are started/stopped in the order they have
> >>> under chkconfig. 90 means it's one of the last ones to be stopped.
> >>>
> >> This is incorrect. From sysvinitfiles:
> >>
> >> # chkconfig: <startlevellist> <startpriority> <endpriority>
> >>
> >> Mikkel
> >
> > After you use chkconfig use /etc/rc.d/rc5.d or whatever runlevels you
> > have selected as a reference. All scripts on shutdown run in reverse
> > order of the startup sequence. So the S01 process will start before
> > the S02 process and  will shut down after S02.
> >
> No - the shutdown link (K<number><name> is created based on the
> <endpriority> number. The startup link (S<number><name>) is created
> based on the <startpriority>. While an <endpriority> of
> 100-<startpriority> is recommended, it is not a fixed rule. This is
> to allow flexibility when you need to stop a process in a different
> order then starting it. This is all well documented in the
> sysvinitfiles file in the initscripts documentation.
> (/usr/share/doc/initscripts-8.45.7 on this system.)
>
> You might also want to read the chkconfig man page. Here is what it
> has to say about it:
>
> RUNLEVEL FILES
>  Each service which should be manageable by chkconfig needs two or
>  more commented lines added to its  init.d  script. The first line
>  tells chkconfig what runlevels the service should be started in by
>  default, as well as the start and stop priority levels. If the
>  service should not, by default, be  started  in any runlevels, a -
>  should be used in place of the runlevels list. The second line
>  contains a description for the service, and may be extended across
>  multiple lines with backslash continuation.
>
>       For example, random.init has these three lines:
>       # chkconfig: 2345 20 80
>       # description: Saves and restores system entropy pool for \
>       #              higher quality random number generation.
>       This says that the random script should be started in levels
>       2, 3, 4, and 5, that its start priority should be 20, and
>       that its stop priority should be 80. You should be able to
>       figure out what the description says; the \ causes the line
>       to be continued. The extra space in front of the line is
>       ignored.
>
> Mikkel

Thanks, I got it straightened out.

So depending upon runlevels selected one would examine rc1.d through
rc5.d to verify the startup sequence. /etc/rc.d/rc0.d is where to
check and verify the shutdown sequence.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux