Originally Posted by jiml8
The variable $OPTIONS should be unset since it isn't set anywhere in that script. But you'd get an "illegal instruction" if it is set improperly.
As root, enter "echo $OPTIONS" and report on what it says. Should give a blank line.
Not entirely accurate. You're right that the script does not set the value of OPTIONS, but the script does indeed source other files:
# source function library
# pull in sysconfig settings
[ -f /etc/sysconfig/sshd ] && . /etc/sysconfig/sshd
I used Red Hat many moons ago. The functions file contains generic utilities used across all startup scripts. Granted, this is CentOS, but I see no reason why they'd change things.
My bet would be that /etc/sysconfig/sshd is where OPTIONS gets set. Also, if I'm not mistaken, those sysconfig files are updated through some gui helper-config app. So, I'm thinking the OP used that app, changed some things without knowing exactly what was going on.
And if I'm right, OPTIONS wouldn't be an environment variable--meaning that trying to echo it wouldn't yield any useful info.
So, amartlk, please post the entire contents of /etc/sysconfig/sshd.