Here at UNC we have solaris machines running OS 5.7 in 32-bit mode
and solaris machines running OS 5.7 in 64-bit mode, both with AFS 3.6. This is
causing problems because "fs sysname" returns the same string: "sun4x_57".
Other applications (for example, lsf) use different binaries depending
on whether they are being run on a 64-bit or a 32-bit machine. We use the
@sys string to determine the correct version of the binaries to invoke.
However, since the @sys name is the same for both machines we can't do that.
I wrote Transarc, asking if there would eventually be different sysnames
for the 32- and 64-bit versions of AFS 3.6. They said both versions will
have the sysname "sun4x_57".
Our initial thought was to set sysname ourself, using "sun4u_57" for
64-bit machines and "sun4x_57" for 32-bit machines. Ah, but then what
do you do about 64-bit machines running in 32-bit mode? And of
course the AFS "sys" command will always return "sun4x_57"; we'd have to modify
that binary as well...
Has anyone else run up against this? Any thoughts on how to
address the problem?
Thanks in advance,
Brian Biswas
