The current init script is bogus for openrc since env isn't a deamon and returns. probably running erl with the -name option could work alike
I've noted the start up issue too, but I don't understand your suggestion. But please feel free to modify/bump/do whatever you'd like to do to this to make it better! :)
I misunderstood completely the erl parameter (my setup seems to miss the manpages), still I'll give a try soon
One thing I've tried here is: start-stop-daemon --start --quiet --chuid jabber:jabber -e HOME=/var/run/jabber \ --exec /usr/bin/ejabberd -- -noshell -detached I still get an error on startup, but at least "env" isn't being used anymore.
something alike export HOME=/var/run/jabber su -m -c /usr/bin/ejabberd jabber could be an 1/2 solution maybe?
works for me if you're happy with it (providing that su is installed on the machine).
The su solution is kinda uncool... Roy, do you have any ideas?
The su solution is the correct one - /usr/sbin/ejabberd is just a script that in turn launches daemons. As such it should not be used with s-s-s. So either use the su soltuion OR put that script into the init script and use s-s-d for the real daemons.
(In reply to comment #7) > The su solution is the correct one - /usr/sbin/ejabberd is just a script that > in turn launches daemons. As such it should not be used with s-s-s. > > So either use the su soltuion OR put that script into the init script and use > s-s-d for the real daemons. > So which solution do the portage maintainers want? I don't want to implementation a solution that won't be acceptable :-)
The only reason to move the logic of /usr/sbin/ejabberd to /etc/init.d/ejabberd would be so that OpenRC can track the daemons to ensure they are still running. Otherwise there is no gain.
*** Bug 255362 has been marked as a duplicate of this bug. ***
JFI: With version bump, I'm going to make init script just a wrapper around ejabberdctl. Probably there should be another way around, but without close work with upstream, I'd better not go any different way.
Should be fixed in 2.1.4.