Persistent /etc/system parameters?
tizzo_at_computer.org
Date: 09/29/05
- Previous message: spam.sink_at_volcanomail.com: "Re: Unable to Boot ULTRA 5"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 29 Sep 2005 12:57:44 -0700
Hi. First a little background. I'm working on a script to automate,
as much as possible, the installation of an application including the
Postgres database server. Postgres has some specific requirements for
tunable parameters under Solaris -- requirements that are not met by
default. It was fairly easy to find the instructions for modifying
these parameters -- simply add the appropriate lines to /etc/system
(after making a backup, of course), and reboot.
Since this installation script will in many cases be run by
non-administrators, I've included logic in it to check the current
values of all relevant parameters, compute what the appropriate values
need to be, and modify the /etc/system file as necessary, after which I
tell the user to reboot.
Now, where I run into trouble is when I try to test the script. You
see, in the process of developing the script, I made all the
appropriate modifications manually, and installed and started the
server to make sure I had it all right. To test the script logic, I
uninstalled the server, restored my /etc/system file to it's original
state, and rebooted, expecting my SHM and SEM parameters to go back to
what they were originally -- not set at all. Instead, I'm finding that
these parameters are all set to what my /etc/system file contained
before I reverted back to the original. My script correctly detects
that everything is hunky-dory and goes ahead and installs and
configures the database.
That's fine, but I'm trying to test the logic that detects and corrects
deficiencies in the tunable parameter values. I'm perplexed as to why
my tunable parameters are absolutely fine, when I've gone out of my way
to try to make sure that they are not. I've quadruple checked the
/etc/system file, and I'm not specifying any of the SHM or SEM
parameters, which is the original state of the system. I've also
quadruple checked the output of the sysdef command, and the parameters
absolutely still have the same values they had before I tried to revert
them. So the script is not making a mistake in detecting that the
parameters are OK -- they actually are OK.
I'm running Solaris 7 on SPARC hardware (Sun Ultra 5 to be exact).
Does anyone know where, other than /etc/system, Solaris may be getting
it's instructions about how to set the SHM and SEM parameters? Any
ideas on how to get them back to the original state so that I can test
my script? Thanks in advance.
Tony
- Previous message: spam.sink_at_volcanomail.com: "Re: Unable to Boot ULTRA 5"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
