[25957] in Athena Bugs
Re: Question/Problem with ATHENA_SYS in lockers
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Aug 18 13:55:44 2004
From: Greg Hudson <ghudson@mit.edu>
To: Tom Cavin <cavin@mit.edu>
In-Reply-To: <16675.34152.806710.141219@lap1-wccf.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1092851719.26687.11.camel@equal-rites.mit.edu>
Mime-Version: 1.0
Date: Wed, 18 Aug 2004 13:55:19 -0400
cc: Athena Bugs list <bugs@mit.edu>
Errors-To: bugs-bounces@mit.edu
The "sys" command ships with OpenAFS and displays the system value
determined by the OpenAFS build system. We don't recommend its use in
any context, and perhaps should not be installing it.
The "fs sysname" command displays the AFS system value as determined at
runtime, which (on an Athena system) should generally agree with
$ATHENA_SYS and the output of "machtype -S" (where machtype is an
Athena-specific command). The output of "fs sysname" is what AFS will
evaluate @sys to in a pathname or symlink value.
AFS has no fallback mechanism for resolving @sys values; it only tries
one thing. The Athena locker system does have a fallback mechanism (the
values listed in $ATHENA_SYS_COMPAT, which should generally agree with
the output of "machtype -C"), but that mechanism only affects the "add"
and "athdir" commands.
The lockers(7) man page describes some of this stuff, and recommends
that you do not use @sys within lockers except for a convenience "bin"
symlink (to be used only by users, not by scripts within the locker) at
the top level.
