qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Stitcher (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-1834) Misconfiguration of config path for Debian libsasl2-2 (SASL support)
Date Fri, 01 May 2009 15:42:30 GMT

    [ https://issues.apache.org/jira/browse/QPID-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705024#action_12705024

Andrew Stitcher commented on QPID-1834:

It looks to me that this would be best addressed during package configuration (autoconf/cmake).
In fact Makefile.in is already generated by automake so there must be a modicum of work in
this direction, perhaps it's just the default configuration that's wrong.

> Misconfiguration of config path for Debian libsasl2-2 (SASL support)
> --------------------------------------------------------------------
>                 Key: QPID-1834
>                 URL: https://issues.apache.org/jira/browse/QPID-1834
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>    Affects Versions: M4
>         Environment: Debian "squeeze"
>            Reporter: Garrett Smith
> The libsasl2-2 package is configured with the option:
>   --with-configdir=/etc/sasl:/usr/lib/sasl2
> Background on this decision can be found here:
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211156
> cpp/etc/Makefile.in specifies SASL_CONF as /etc/sasl2, which isn't on the config path
that the Debian package is compiled with. The result is that the qpid sasl configuration is
never used. This is a pain to debug as the missed configuration is silently ignored.
> I'm not sure what the ideal solution is here, but I think this ought to be addressed
given we're talking about Debian.
> A config option for qpidd would probably be appropriate, or, in keeping with the hard
coding strategy, create a link from /etc/sasl to /etc/sasl2. Just a couple ideas though.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message