You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got an init.d script that starts eye. It appears that during boot, there is no HOME variable set. Makes sense. Except this causes eye to fail (HOME undefined, should be HOME or EYE_HOME environment).
I noticed that if I configure EYE_HOME, it will put the pid and socket files there. When I login and check eye's status, it looks in the default /var/run/eye directory, can't find them, and complain that the server is not running. I've worked around the issue by defining export HOME=/root at the top of my init.d script.
Is this expected behavior?
Thanks!!
Norman
The text was updated successfully, but these errors were encountered:
I've got an init.d script that starts eye. It appears that during boot, there is no HOME variable set. Makes sense. Except this causes eye to fail (
HOME undefined, should be HOME or EYE_HOME environment
).I noticed that if I configure
EYE_HOME
, it will put the pid and socket files there. When I login and check eye's status, it looks in the default/var/run/eye
directory, can't find them, and complain that the server is not running. I've worked around the issue by definingexport HOME=/root
at the top of my init.d script.Is this expected behavior?
Thanks!!
Norman
The text was updated successfully, but these errors were encountered: