Very Computer

Interesting problem!

at is an SUID program.  For security reasons, LIBPATH is removed by
exec when an SUID program is invoked - to prevent the caller from
inserting a bogus library!  So "at" never sees the value of LIBPATH you
are running with when you invoke it!

I would advise writing the shell script to set the value.  You could
put it in another environment variable, and have the shell script be,
for example:

#!/bin/ksh
export LIBPATH=$MYLIBPATH
exec $*
--

|>
|> Is there a way around this other than creating scripts which determine which
|> version I want, set the LIBPATH, then call the real application?  I really
|> want LIBPATH to be treated as any other environment variable in this case.

You might try letting your command line look like

export LIBPATH=/directory2 && your_cmd_goes_here

If you feed this to at, I believe it will set up the environment
as desired.

The problem is that "at" is a setUID program.  As such, LIBPATH is
filtered by it, so you'll have to make the LIBPATH part of the command
to execute.

--
________________________________________________________________________
Gary R. Hook                         | "It's hard to work in groups
AIX Application Enabling             | when you're omnipotent."
IBM Corporation, Southlake, Texas    |  - Q in Star Trek: The Next
The above opinions are all mine.     |    Generation