Date: Tue, 17 Mar 2009 19:52:27 +0000 (GMT) From: Neil Darlow <neil@darlow.co.uk> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/132758: ejabberd spool directory is incorrect Message-ID: <20090317195227.9DE27102CF4@router.darlow.co.uk> Resent-Message-ID: <200903172020.n2HKKAvw057725@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 132758 >Category: ports >Synopsis: ejabberd spool directory is incorrect >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Mar 17 20:20:10 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Neil Darlow >Release: FreeBSD 7.1-RELEASE-p3 i386 >Organization: >Environment: System: FreeBSD router.darlow.co.uk 7.1-RELEASE-p3 FreeBSD 7.1-RELEASE-p3 #0: Tue Feb 17 10:31:01 GMT 2009 root@router.darlow.co.uk:/usr/obj/usr/src/sys/ROUTER i386 >Description: ejabberd-2.0.3 incorrectly uses /var/spool/ejabberd/ejabberd for its spool directory. This makes it impossible to migrate from an earlier version of ejabberd because the existing database structure is ignored. Also, at startup, ejabberd attempts to create the spool directory which will cause a problem with permissions when it is corrected to /var/spool/ejabberd. >How-To-Repeat: Try running an upgraded ejabberd with an existing spool directory in /var/spool/ejabberd and note that /var/spool/ejabberd/ejabberd is created with a new database structure in it. >Fix: Needs further analysis and testing before deploying as stable version. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090317195227.9DE27102CF4>