[23657] in Athena Bugs
Re: Alex T Prengel: strange path-related launch problem with gathrun/attachandrun
daemon@ATHENA.MIT.EDU (Garry Zacheiss)
Mon Aug 18 20:29:20 2003
Message-Id: <200308190029.h7J0TIuI013835@brad-majors.mit.edu>
To: Alex T Prengel <alexp@MIT.EDU>
cc: bugs@MIT.EDU, jamous@MIT.EDU, csnowden@MIT.EDU
In-Reply-To: Your message of "Mon, 18 Aug 2003 20:19:25 EDT."
<200308190019.h7J0JPCL007574@dit.mit.edu>
Date: Mon, 18 Aug 2003 20:29:18 -0400
From: Garry Zacheiss <zacheiss@MIT.EDU>
>> among which, that I didn't know exactly what gathrun and attachandrun
>> are supposed to do,
For the record, gathrun is just a shell script that calls attachandrun;
it uses gdialog to report an error to the user in the case of a binary
not being available, because its intended purpose was to be used in
cases where it doesn't have access to the user's terminal to print an
error message (because the application is being run from the gnome
panel).
attachandrun mostly does what it sounds like; it attaches a locker and
runs the named binary, i.e.: "attachandrun moira moira moira" attaches
the moira locker and exec's the binary named "moira" out of it with an
argv[0] of "moira". If run with the --check option, attachandrun just
verifies the existance of the binary (by looking for
/mit/lockername/arch/$ATHENA_SYS/bin/binary) and reports success or
failure via its exit status.
Neither is supposed to modify your PATH or anything else in your
environment.
Garry
