Linux Newbie help
 help / color / mirror / Atom feed
From: Arthur Othieno <arthurothieno@gmx.net>
To: Paul Kraus <pkraus@pelsupply.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: More on Startup Scripts
Date: Wed, 18 Sep 2002 20:55:57 +0100	[thread overview]
Message-ID: <3D88DA4D.80502@gmx.net> (raw)
In-Reply-To: 009101c25f3b$c47471b0$64fea8c0@pkrausxp

Well, if for example your default runlevel is 5, then in the /etc/rc5.d 
directory (in Debian) (or /etc/rc.d/rc5/ in RedHat and RedHat-like 
systems), you may have a listing like this (this is just an example)

K12anacron  -> /etc/init.d/anacron
S02portmap  -> /etc/init.d/portmap
S11sshd     -> /etc/init.d/sshd
S43sendmail -> /etc/init.d/sendmail

...note that these are actually _not_ scripts but symbolic links to the 
actual scripts that reside in /etc/init.d, thus, in the above example, 
anacron will be killed, the portmapper started, followed by sshd and so 
on. The numbers XX dictate the order in which services are started/stopped.

Arthur

Paul Kraus wrote:

> I understand that in the runtime folders that the SXXscript stands for
> startup and the KXXscript stands for kill. What do the XX stand for?
> 
> Paul Kraus
> Network Administrator
> PEL Supply Company
> 216.267.5775 Voice
> 216-267-6176 Fax
> www.pelsupply.com
> 


-
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

      parent reply	other threads:[~2002-09-18 19:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18 17:49 More on Startup Scripts Paul Kraus
2002-09-18 18:14 ` Ray Olszewski
2002-09-18 19:55 ` Arthur Othieno [this message]

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=3D88DA4D.80502@gmx.net \
    --to=arthurothieno@gmx.net \
    --cc=linux-newbie@vger.kernel.org \
    --cc=pkraus@pelsupply.com \
    /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