KenCunningham
Technical User
Hi folks, hopefully a quickie - how does one change the number of commands to be stored in the .sh_history file in AIX 5.2. I had thought it might be the $HISTSIZE variable, but this is related to password reuse. TIA.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
.sh_history size
- Thread starter KenCunningham
- Start date
- Status
Hi Ken,
I agree with you on it being the HISTSIZE env var, but cant be sure at 5.2. Its is definately the case at 4.3 and 5.1 so I would think it would be the same for 5.2.
One interesting aspect of its use under AIX is that it seems to allocate storage based off this var on execution of ksh (ie. it does not look like its dynamic).
This means that you will not see the affects of your change within the current shell. If you run ksh again though (after exporting your HISTSIZE var) you should see your change manifest.
If someone knows how to alter this characteristic within your current shell (in AIX) .... I'd be very interested to hear it ;-)
All the Best Bud
____________________
Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debuging Mondays code.
I agree with you on it being the HISTSIZE env var, but cant be sure at 5.2. Its is definately the case at 4.3 and 5.1 so I would think it would be the same for 5.2.
One interesting aspect of its use under AIX is that it seems to allocate storage based off this var on execution of ksh (ie. it does not look like its dynamic).
This means that you will not see the affects of your change within the current shell. If you run ksh again though (after exporting your HISTSIZE var) you should see your change manifest.
If someone knows how to alter this characteristic within your current shell (in AIX) .... I'd be very interested to hear it ;-)
All the Best Bud
____________________
Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debuging Mondays code.
- Thread starter
- #3
KenCunningham
Technical User
Thanks pal, I think maybe I was confusing histsize and HISTSIZE. I've got a test system I can play on, so I'll see what happens when I change it. Have a good weekend!
RodKnowlton
MIS
- Apr 26, 2000
- 1,005
d3vzero,
While technically not the current shell (it overlays the current shell, but keeps the environment), this should effectively be the same:
Rod Knowlton
IBM Certified Advanced Technical Expert pSeries and AIX 5L
While technically not the current shell (it overlays the current shell, but keeps the environment), this should effectively be the same:
Code:
export HISTSIZE=2048
exec /bin/kshRod Knowlton
IBM Certified Advanced Technical Expert pSeries and AIX 5L
LOL,
Yeah .... Thats how I got around it too
It is kind of weird that the attribute was not built to be dynamic in the first place though.
BRgds.
____________________
Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debuging Mondays code.
Yeah .... Thats how I got around it too
It is kind of weird that the attribute was not built to be dynamic in the first place though.
BRgds.
____________________
Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debuging Mondays code.
- Status