Re: RC Scripts question

Claudio Fontana <[email protected]>
Newsgroups gmane.linux.slackware
Message-ID <CAJuRt+oyfHxCw=6M9UXaprr6Q_rqVhf+f+N55R8s46aHeUZ2_w@mail.gmail.com>
Hello,

On Sun, Nov 25, 2012 at 2:44 AM, Nick Edwards <[email protected]> wrote:
> Hi,
>
> Have a question for the "bash/sh" experts.
>
> In the files like rc.M,   in the "if" statements, some scripts have a
> period then space, then called_script start/stop_parameter etc
>
> Now, as I understand it, the period means run called_script with the
> sh environment of rc.6.

info bash

`.    (a period)'
          . FILENAME [ARGUMENTS]
     Read and execute commands from the FILENAME argument in the
     current shell context.  If FILENAME does not contain a slash, the
     `PATH' variable is used to find FILENAME.  When Bash is not in
     POSIX mode, the current directory is searched if FILENAME is not
     found in `$PATH'.  If any ARGUMENTS are supplied, they become the
     positional parameters when FILENAME is executed.  Otherwise the
     positional parameters are unchanged.  The return status is the
     exit status of the last command executed, or zero if no commands
     are executed.  If FILENAME is not found, or cannot be read, the
     return status is non-zero.  This builtin is equivalent to `source'.

> Am I correct in assuming this means if I set the ulimit to 8192 for
> rc.M  that all called scripts will get a ulimit raise to 8192?
>
> Also, conversely if I call, say,  rc.httpd with a ulimit of 8192 will
> that be honored or ignored?

Why don't you try it, and let us know?
`ulimit -a' reports all current limits.

> Or, do I have the period (source???) all wrong (highly probably since
> google is full of so much mis-information)?
>
> Niki

Ciao,

Claudio
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.