As this crashed the server and caused it to reboot, would any of you know whether it would cause on reboot /etc/environment not to be read ?
I ask as out Informix databases did not start when running smitty clstart, and the DB experts reckon it was due to EXTSHM=ON not being set from /etc/environment
A reboot is a reboot, for whatever cause. It should (and will) have read /etc/environment.
You can check the startup ENV with:
[tt]ps eww (cronPID)|tr ' ' '\n'|grep =[/tt]
Choose any system daemon's pid that hasn't been restarted yet.
Make sure that the shell from where you ran the smitty clstart has the correct environment. Also the start scripts may want some screening for correct ENV behaviour...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.