Linux-admin Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Salmon <Michael.Salmon@uab.ericsson.se>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: significance of 2 digit number in rc.d directory.
Date: Thu, 06 Jun 2002 08:44:58 +0200	[thread overview]
Message-ID: <180000.1023345898@uabs78c65> (raw)
In-Reply-To: <3CFECF49.8010704@baywinds.org>

On Wednesday, June 05, 2002 07:56:09 PM -0700 Bruce Ferrell 
<bferrell@baywinds.org> wrote:
+------
| I was under the impression that the scripts executed in numerical order.
| They do under Solaris anyway
|
| rich+ml@lclogic.com wrote:
|
| > There really is no significance. The scripts are executed in
| > alphabetical order (somebody does "for script in S*; do exec $script
| > start; done"), and the two digit sequence is a typographical convention
| > to make it easy to manage that order.
| >
| > == Rich
| >
| > On Wed, 5 Jun 2002, Mohammed Khalid Ansari wrote:
|
| >> I have seen that the files in rc.d directory starting with either S or
| >> K are followed by two digit number. I understand that S stands for
| >> start and K for kill but what is the significance of the numbers that
| >> followed.
+-----X8

Sorry but in Solaris they execute in ascii order, the code that executes 
them is:

for f in /etc/rc0.d/S*
do
  if [ -s $f ]
  then
    case $f in
      *.sh)   . $f ;;
      *)      /sbin/sh $f start ;;
    esac
  fi
done

The fact that there are usually 2 digits after the S is purely a convention.

/Michael
--
This space intentionally left non-blank.

      reply	other threads:[~2002-06-06  6:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05 10:53 significance of 2 digit number in rc.d directory Mohammed Khalid Ansari
2002-06-05 11:02 ` John Hallam
2002-06-05 17:49 ` rich+ml
2002-06-06  2:56   ` Bruce Ferrell
2002-06-06  6:44     ` Michael Salmon [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=180000.1023345898@uabs78c65 \
    --to=michael.salmon@uab.ericsson.se \
    --cc=linux-admin@vger.kernel.org \
    /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