Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start with init.d script #214

Open
normelton opened this issue Jun 1, 2018 · 1 comment
Open

Unable to start with init.d script #214

normelton opened this issue Jun 1, 2018 · 1 comment

Comments

@normelton
Copy link

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

@kostya
Copy link
Owner

kostya commented Jun 1, 2018

HOME not required for root user, but for custom user HOME should be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants