Richard Hawes <[EMAIL PROTECTED]> wrote:
> Sentence 2 of paragraph 1 says: "These scripts should be named
> /etc/init.d/package,"
> when should scripts have a .sh suffix?
>
> rc and rcS scripts optimize by sourcing .sh scripts
> All bash scripts could be sourced
>
> Should all scripts be bash scripts
> or should all bash compatible scripts have a .sh suffix
> Is the .sh suffix just a matter of historical use or does it matter?
Someone replied:
> There needs to be something about the fact that rcS scripts matching
> the pattern *.sh are sourced by /etc/init.d/rcS; and should not
> necessarily be required to support all of the standard arguments.
Rereading the relevant section of policy, I can see where the
confusion arises. There are two distinct types of script in
/etc/init.d (not including rc and rcS): there are those which start
and stop services, such as sysklogd, and there are those required for
system startup and/or shutdown, such as mountall.sh. However, the
policy as written only describes the former.
Does anyone have a suggestion as to how to rewrite things to better
describe reality?
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED]
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
