Re: [Testbed-admins] How to add more Emulab admin account

[Robert P Ricci <ricci@cs.utah.edu>]

The simplest way to make sure that the right files got installed would
be to grep through the source for '@ISOLATEADMINS@' to see what files
use it, then look at your configured tree to make sure '@ISOLATEADMINS@'
got replaced with '0', then make sure those files in your configured
tree match the ones that got installed into /usr/testbed . This will
tell us where along in the process the change didn't get carried
through.

Thus spake chunhui Zhang(Evan) on Thu, Dec 17, 2009 at 06:39:02PM -0500:
> Still no luck. I begin to suspect the way I did re-install, what I did were,
> 
> 1) cvs up
> 2) cd /usr/testbed/obj/testbed
> 3) sudo /usr/testbed/src/testbed/configure
> --with-TBDEFS=/path/to/my/defs/file
> 4) sudo gmake
> 5) sudo gmake boss-install
> 
> Are there any other steps that I need? I did not reboot boss. is this ok?
> 
> Evan
> 
> On Thu, Dec 17, 2009 at 6:09 PM, Leigh Stoller <stoller@flux.utah.edu>wrote:
> 
> > Updated successfully with ISOLATEADMINS=0 in defs file. However, new
> >> user seems still can not join project 'emulab-ops',
> >>
> >
> > It is possible that not all the file got rebuilt. This is the problem
> > you mentioned the other day. I just committed a fix to GNUmakerules in
> > the toplevel directory. Why don't you cvs update that file, then
> > rebuild and reinstall, and then try again.
> >
> > Basically, all of the *.in files now depend on config.status, so
> > anytime you run configure, any files that did not get configured
> > (cause they are missing from the giant file list) will get rebuilt.
> >
> > Lbs
> >
> >

> _______________________________________________
> Testbed-admins mailing list
> Testbed-admins@flux.utah.edu
> http://www.flux.utah.edu/mailman/listinfo/testbed-admins