Package: ejabberd Version: 1.1.1-8 Severity: wishlist 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. In my case, my ejabberd node is "srv-castle" (and it does not accept requests from ejabberdctl which are sent out to srv-castle1 or srv-castle2, even though they map to the same computer); nevertheless, the internals of ejabberdctl always calculate the node name as [EMAIL PROTECTED] -s`, what is deadly wrong for any configuration similar to mine one. In particular, this leads to complete inability to control the service from /etc/init.d, therefore from dpkg scripts on package upgrade. 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. A long-term suggestion (discussable) is to ensure that the node name cannot ever get out of sync with ejabberdctl; if the node name is an user-defined variable and is requested by debconf (what is more convenient, IMO), this definition should be used by ejabberdctl, and may go to somewhere like /etc/ejabberdctl; if the node name is always dynamically generated during the setup from hostname (what seems wrong, as the node name is an excessively important thing for an ejabberd installation), it should be generated and always used utilizing the same algorithm.
-- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i586) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-486 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages ejabberd depends on: ii adduser 3.97 Add and remove users and groups ii debconf [debconf-2.0] 1.5.4 Debian configuration management sy ii erlang-base 1:11.b.1-1 Concurrent, real-time, distributed ii erlang-nox 1:11.b.1-1 Concurrent, real-time, distributed ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libexpat1 1.95.8-3.2 XML parsing C library - runtime li ii libssl0.9.8 0.9.8b-3 SSL shared libraries ii openssl 0.9.8b-3 Secure Socket Layer (SSL) binary a ii ucf 2.0014 Update Configuration File: preserv ii zlib1g 1:1.2.3-13 compression library - runtime ejabberd recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
