Date: Thu, 4 Dec 2003 13:19:52 -0600 (CST) From: Bob Van Valzah <Bob@VanValzah.Com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/59961: Jabber deamon won't run if hostname is mixed case Message-ID: <200312041919.hB4JJqrC009238@Air.EmRav.Com> Resent-Message-ID: <200312041930.hB4JUAtG084615@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 59961
>Category: ports
>Synopsis: Jabber deamon won't run if hostname is mixed case
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Dec 04 11:30:09 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Bob Van Valzah
>Release: FreeBSD 4.8-RELEASE-p7 i386
>Organization:
EmRav.Com
>Environment:
System: FreeBSD Air.EmRav.Com 4.8-RELEASE-p7 FreeBSD 4.8-RELEASE-p7 #0: Sat Sep 20 11:02:09 CDT 2003 bob@Air.EmRav.Com:/usr/obj/usr/src/sys/TWINHEAD i386
Jabber port version 1.4.2
>Description:
If hostname contains mixed case, jabber daemon can't deliver messages.
Apparently this is because the hostname is internally lower cased
and compared against what's supplied on the command line with the
-H option from jabberd.sh. It's possible that this happens only
with mixed-case, fully-qualified domain names.
>How-To-Repeat:
Start up jabberd and try to deliver a message with a client. You get a
message like this:
20031204T18:28:36: [notice] (air.emrav.com): bouncing a routed packet to bob@air.emrav.com from 14@c2s/80DC280: Internal Delivery Error
>Fix:
Apply the following patch to jabberd.sh as distributed with the port:
--- /usr/local/etc/rc.d/jabberd.sh Thu Dec 4 12:35:39 2003
+++ /usr/ports/net/jabber/files/jabberd.sh Sun Sep 1 03:20:31 2002
@@ -7,7 +7,7 @@
USER="jabber"
RUNDIR="/var/tmp"
-HOSTNAME=`/bin/hostname | tr '[A-Z]' '[a-z]'`
+HOSTNAME=`/bin/hostname`
test -x ${PREFIX}/sbin/jabberd || exit 1
While you're fixing jabberd.sh, might be a good idea for the jabberd
port to be consistent with others like apache. The port could install
the startup script into jabberd.sh-dist and also copy this into
jabberd.sh if one didn't already exist. That'd allow for the
preservation of local initialization changes across portupgrades.
Thanks!
Bob
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312041919.hB4JJqrC009238>