Bug 3946 – don't set $SASL_PATH unnecessarily

Bug 3946 - don't set $SASL_PATH unnecessarily

Summary:

don't set $SASL_PATH unnecessarily

Status:	RESOLVED FIXED

Product:	Toolkit Internals
Component:	globus_common
Version:	4.0.1
Platform:	All All

Importance:	P3 minor
Target Milestone:	4.0.2
Assigned To:	Mike Link

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-11-28 15:50 by Jim Basney
Modified:	2006-04-18 10:58 (History)

Attachments
patch to set $SASL_PATH only if $GLOBUS_LOCATION/lib/sasl exists (5.91 KB, patch) 2005-11-28 15:53, Jim Basney	Details
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Jim Basney 2005-11-28 15:50:31

Cyrus SASLv2 looks for plugins in /usr/lib/sasl2 unless $SASL_PATH is set in
the
environment to override the default path.  The globus-user-env.* and
globus-script-initializer scripts set SASL_PATH=$GLOBUS_LOCATION/lib/sasl even
if $GLOBUS_LOCATION/lib/sasl doesn't exist, causing problems for other software
using the default Cyrus SASLv2 installation on the system (such as MyProxy). 
Given that the globus_cyrus_sasl packages aren't installed by default and are
only installed for the deprecated MDS2 packages, I suspect it's common for
$GLOBUS_LOCATION/lib/sasl not to exist in a GT installation.  Please consider
applying the patch below to set $SASL_PATH only if $GLOBUS_LOCATION/lib/sasl
exists.

------- Comment #1 From Jim Basney 2005-11-28 15:53:33 -------

Created an attachment (id=762) [details]
patch to set $SASL_PATH only if $GLOBUS_LOCATION/lib/sasl exists

------- Comment #2 From Charles Bacon 2005-11-29 14:10:08 -------

Commited to HEAD and globus_4_0_branch.

Thanks Jim!