Today, Patrick J. O'Rourke gleaned this insight:
>
> > You can do it any time, but as a practical matter you don't generally
> > change this value once you figure out what you need it to be, and you
> > generally will always need it to be set to that value, so in general it's
> > something you'd want to do at boot time.
>
> Right. I thought that Bruce was implying that it _had_ to be done at
> boot time. When I had an application which required me to change this,
> I just set in the script which kicked off the application (granted it
> was the only thing running on the machine).
It's more a philosophy/history thing... maybe 2 factors at work. On older
Unix kernels you don't change parameters of a running system. Linux can
do it quite easily but I think there's still a stigma which says if ya
gotta muck with parameters, do it once at boot time and don't touch it.
Also I think sysadmins generally think from a system configuration
standpoint rather than an application standpoint. Changing a kernel
parameter is a system configuration, so it goes in the system
configuration scripts (rc scripts) and not in an application start-up
script.
Really there's no reason it can't be done either way, but I'd bet ya at
least 90% of Linux admins out there do it at boot time.
[That sounds like it should be a bumper sticker or something... :) ]
--
You know that everytime I try to go where I really want to be,
It's already where I am, cuz I'm already there...
---------------------------------------------------------------
Derek D. Martin | Unix/Linux Geek
[EMAIL PROTECTED] | [EMAIL PROTECTED]
---------------------------------------------------------------
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
