Added sname use flag to change behavior of erlang node starting ejabberd in /usr/bin/ejabberd and /usr/bin/ejabberdctl The behavior of erlang differs fundamentally when starting a beam whether -sname or -name was used. The sname use flag modifies the ejabberd script to use the corresponding argument. I also added the http_bind patch. This has been tested on two x86 boxes and works. Reproducible: Always
Created attachment 106290 [details] full ebuild this is modified ebuild that has the http_bind and sname use flags
Created attachment 106294 [details, diff] http-bind.patch The patch for http bind. source: http://www.jabber.ru/bugzilla/show_bug.cgi?id=91
The http-bind is not yet applied upstream, and genuine concerns were raised in November 2006 that still have not been answered. I am not willing to apply this patch to the ebuild as a result. Could you properly document the difference between between name & sname so it can be explained in a USE-flag description.
Comment on attachment 106294 [details, diff] http-bind.patch Patch not acceptable.
The -sname and -name are documented at http://www.process-one.net/docs/ejabberd/guide_en.html#htoc12 the -sname will use `hostname -s` to communicate with the node. and -name will will use `hostname -f`. I am not an erlang expert, but -name works best for me.
Created attachment 114560 [details, diff] updated patch for 1.1.3 I have updated the patch for 1.1.3 ebuild I have kept the sname use flag and related changes Instead of applying the http_bind patch directly in the ebuild via a useflag, I have moved it out to a general patch dir. Modeled after the mail-mta/netqmail patch dir. To use, just specifiy EJABBERD_PATCH_DIR in /etc/make.conf and it will slurp all patches in the dir and apply them.
With the exception of the http_bind patch (which is not acceptable for reasons detailed above), your changes have made it into the 1.1.3-r1 ebuild of ejabberd. Thank you for your bug report :)
