On Wed, Sep 06, 2006 at 09:06:42AM +1000, [EMAIL PROTECTED] alleged:
> My understanding is as follows:
>
> When you configure maui there is an option --with-key=XXX
> If you use it, a 'key' is configured into the binaries and used as part
> of the client-command to server authentication. If you don't specify
> it, a random key is used in the build. As a result, if you want the
> client tools from one build to work with another build, you must specify
> the same key to configure.
>
> I'd happily be corrected if this is wrong or incomplete.
>
> Note. I presume you are using either the new clients with the old maui
> or old clients with a new maui. The solution is 1) use the new clients
> with the new maui, and 2) in the future specify a particular key so that
> the problem will not recurr even if you use old clients.
I've this patch hanging around in my build sys for awhile to give
long-term consistent seeds.
And put this in your ~/.bash_profile:
export MAUI_BUILDSEED=xxxx
--- maui-3.2.6p14/configure.ac_orig 2005-07-11 12:53:33.000000000 -0700
+++ maui-3.2.6p14/configure.ac 2005-07-11 12:57:24.000000000 -0700
@@ -29,8 +29,13 @@
AC_SUBST(MACHINE)
# Handle Checksum seed
+if test "${MAUI_BUILDSEED+set}" = set; then
+ SEED="$MAUI_BUILDSEED"
+else
+ SEED=$RANDOM
+fi
AC_ARG_WITH(key,
- [ --with-key=SEED security checksum key (defaults to a random
integer)], SEED=$withval, SEED=$RANDOM)
+ [ --with-key=SEED security checksum key (defaults to a random
integer)], SEED=$withval)
AC_SUBST(SEED)
# Determine OPSYS
_______________________________________________
mauiusers mailing list
[email protected]
http://www.supercluster.org/mailman/listinfo/mauiusers
