We've done that for the users, but what if a script using this module is being run in a non-interactive capacity (such as via cron or another program that does not necessarily load environment settings from /etc/profile)? The idea is to make this module as absolutely self-contained as possible, and functional with little if any change to the environment as possible.

In this specific case, the module was being called via a CGI script under Netscape server. My solution was just to add an appropriate LD_LIBRARY_PATH as an environment variable NES passes to its CGI scripts, but I view this as a messy fix, since it doesn't work towards my goal of making the module self-contained. It will do, though, and I don't think we'll have many more (if any) issues like this to deal with in the future.