On 9/27/06, Alexander Myodov <[EMAIL PROTECTED]> wrote:
There may be configurations, when the node name of installed ejabberd is not equal to [EMAIL PROTECTED] -s` (as calculated by /usr/sbin/ejabberdctl) - actually, I have one; I cannot remember whether it was reportbug where I defined the node name, but I didn't do any hacky stuff, different from usual ejabberd installation. I have a setup where the hostname of the server is "srv-castle.pvt", while inside DNS it is just an alias to another hostname, "srv-castle2.pvt"; in my case, it leads to the fact that while "hostname" shows "srv-castle.pvt", "hostname -s" shows "srv-castle2", what is different.
Yes, it's possible tah erlang has very special view on hostname. In the next package version we'll remove `hostname -s` from ejabberdctl script and let erlang chose hostname.
Short-term suggestion is to invent a variable in /etc/default/ejabberd like NODE_NAME, and read /etc/default/ejabberd from /usr/sbin/ejabberdctl; if the variable is defined, its value will be assigned to NODE variable; therefore, an owner of a configuration similar to mine one will be able at least to set this variable allowing ejabberdctl to work.
The idea seems to be good. The ejabberd admin should remember, however, that changing node name is a nontrivial task. So, if the hostname doesn't change and given that we ejabberdctl doesn't use `hostname -s` it's better to use default node name. -- Sergei Golovan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
