Thanks to David Smith who was the only one to reply, but
Compaq figured this one out
It looks like my /etc/sysconfigtab got corrupted, the length was more
than
the prescribed limit of 32767.
To verify:
1. get the size of /etc/sysconfigtab
ls -l /etc/sysconfigtab
-rw-r--r-- 1 root system 54410 Sep 5 16:34 /etc/sysconfigtab
2. Get the effective value of /etc/sysconfigtab
/usr/lbin/sysconf
Actual length of /etc/sysconfigtab is 54410
Effective length of /etc/sysconfigtab is 37502
The actual length should be the same as the ls -l output.
The effective length should be smaller than the actual length
and should be less or equal to 32767.
My /etc/sysconfigtab had an effective length greater than 32767!!!
I Restored the old /etc/sysconfigtab from your backup prior to the
patch.
Then rebooted.
And all previous kernel parameters were restored and all was fine :)
------------------------------------------------------------------------
-----
-----Original Message-----
From: REEVE Ruth [mailto:RREEVE_at_goldcoast.qld.gov.au]
Sent: Wednesday, September 05, 2001 7:12 PM
To: tru64-unix-managers_at_ornl.gov
Subject: Tru64 v4.0f Patchkit 6 - problems changing kernel parameters
Hi All,
I have searched the archives but haven't had any luck with this problem
Before installing onto our production machines (Alpha 4100 cluster with
TCR1.6)
I have installed v4.0f patchkit #6 onto a test box (a Digital Personal
WorkStation 600au DECST30) which had v4.0f patchkit #5 already
installed on it. The patchkit installed fine with no errors.
However after the install, I noticed that some of the kernel
variable values were changed (back to the defaults I assume)
even though our settings for these variables were present in
the /etc/sysconfigtab file.
eg. maxusers was changed to 32 (we had it set at 2048)
max-proc-per-user was changed to 64 (we had it set to 512)
This has happened to attributes from various subsystems (ie. ipc,
proc, socket, advfs,inet, vfs, vm, pwrmgr)
I tried to change these variables back to our previously set values
using the follwoing commands :-
/sbin/sysconfigdb -d -t /etc/sysconfigtab ?subsystem
/sbin/sysconfigdb -a -t /etc/sysconfigtab -f
/usr/local/bin/sysparams.mod ?subsystem
doconfig -c ?MACHINENAME
moved in the new /vmunix file and rebooted
This produced no errors, but the attributes values did not change.
The only way I can change an attribute value is by using the command
sysconfig -r ?subsystem ?attribute=?value
But this gets reset on the next reboot.
Has anyone seen a problem like this???
Many thanks
Ruth
(note: the format of the /usr/local/bin/sysparams.mod file is as
follows)
proc:
maxusers = 2048
max-proc-per-user = 512
max-threads-per-user = 4096
ipc:
shm-mni = 1024
shm-seg = 256
shm-max = 67108864
**********************************************************************
This e-mail and its contents is confidential to Gold Coast City Council
and un-authorised use is strictly prohibited.
**********************************************************************
Received on Sun Sep 09 2001 - 22:30:17 NZST