I will have a look through the cmu code then, and fix it and submit the
patch to Hisao, because this should 'just 'work.
Taco
----- Original Message -----
From: "Ken Marcus - Precision Web Hosting, Inc."
<kenmarcus (at mark) precisionweb.net>
To: <coba-e (at mark) bluequartz.org>
Sent: Tuesday, April 11, 2006 11:38 PM
Subject: [coba-e:04565] Re: CMU-import: <admin> and user-sequence
>>>Roman Buerkle said:
>>>we just did a migration from an RAQ4i to a BQ-system and encountered the
>>>following problems:
>>>RAQ4i with "RaQ4-All-CMU Release 2.53" and raqbackup.sh
>>>BQ with BQ-CMU 2.55
>>>- the exported site-admins, declared as <admin value="t"> were imported,
>>>but not set as admins on the BQ. Had to be corrrected >>manually.
>>>- while importing larger sites, users with forwarders to other users of
>>>the same domain, are not correctly imported, because the other >>user was
>>>not already imported.
>>>These forwarders had to be corrected manually afterwards.
>
>>>My question:
>>>- is the interpretation of the admin-flag correctly implemented? Is this
>>>a bug or feature ;-)
>>>- can the sequence of users be set, or can the script be modified to
>>>import "as is".
>
>
> Since the cmu does not set the site-admin, what I do in a single site
> import script is set it manually using the shell tools after the site is
> imported fully imported.
>
> The perl for that is:
> print "What is the admin user for this site, we set it using the shell
> tools. ";
> $adminuser = <STDIN>;
> chomp ($adminuser);
> $adminuser =~ s/ //g;
>
>
> ystem("/usr/sbin/cmoduser --name=$adminuser --enable-admin --adminPassword='$serveradminpassword'
> ");
>
>
> One other problem is if you are importing a user with multiple aliases
> with "admin" being one of them, then no aliases are set and any value for
> forwarding is not set. I think that is a carry-over from the raq 550 CMU.
>
>
>
> ----
> Ken Marcus
> Precision Web Hosting, Inc.
> http://www.precisionweb.net
>
>
>
>
>
>
>
>
>
>
>
>