[Moabusers] Errors with OS X clients talking to Linux server.
Justin Bronder
jsbronder at gmail.com
Fri May 12 13:47:58 MDT 2006
In the August 2005 Archives for this list there was a thread dealing with a
similar issue:
http://www.supercluster.org/pipermail/moabusers/2005-August/000031.html
The advice was to issue the command MOABTEST=checksum:bababa,HMAC64,dog
bin/moab
on the various machines to make sure that the returned CS: string was the
same. The compiled
moab executable is 32-bit in the following examples:
Darwin 8.6.0 (OS X 10.4.6)
root at meldrew-osx:/usr/src/moab-4.5.0# MOABTEST=checksum:bababa,HMAC64,dog
bin/moab
CS: 'TF6HZZG4uTm+lVg1Br5Qae2h4UA='/'gsk7fkGP1zwO4/1IeKtryCfkTeg='
Linux 2.6.16 ppc64
root at meldrew-linux:/usr/src/moab-4.5.0# MOABTEST=checksum:bababa,HMAC64,dog
bin/moab
CS: 'iEQIQX1nhHaXN8gyn5/TYCbJstk='/'5JUSUk9HtBONhQydnYWXKScoHaA='
Linux 2.6.16 x86
root at ldap1:/usr/src/moab-4.5.0# MOABTEST=checksum:bababa,HMAC64,dog
bin/moab
CS: 'iEQIQX1nhHaXN8gyn5/TYCbJstk='/'5JUSUk9HtBONhQydnYWXKScoHaA='
Is there any way around this issue? The moab-private.cfg files are blank
and I did
build the source with the same MBUILD_SKEY, which fixed the problem earlier.
I just want all the users to be able to use the standard commands on these
three
machines.
Thanks in advance,
Justin Bronder
P.S. If anyone wouldn't mind sending me some examples of their
moab.cfgfiles, I'd
be much obliged.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.supercluster.org/pipermail/moabusers/attachments/20060512/8d901e05/attachment-0003.html
More information about the moabusers
mailing list