- 25 Oct, 2005 2 commits
-
-
Mike Hibler authored
# # Argh! dhclient in FreeBSD 5 has a new auto-background "feature", # it dives into the background after 10 seconds regardless of whether # it has received a response. This is fubar for us. Unfortunately, # we cannot just crank this number through the roof because it is based # on a polling interval which actually has a rational purpose. The timeout # is actually (2 * polling_interval) where polling_interval is how often # dhclient rechecks an interface without link. We need to keep this value # reasonable in the event that we boot up and don't immediately have link # on the control net. So lets try 15 seconds (30 second auto-background # timeout) and see how things go. #
-
Leigh B. Stoller authored
-
- 20 Oct, 2005 1 commit
-
-
Mike Hibler authored
So modify my previous hack to look for the first instance of a label= in that case. This hack has now officially transcended Plain Ole Ugly and has entered the realm of Butt Ugly.
-
- 18 Oct, 2005 2 commits
-
-
Mike Hibler authored
groklilo when setting root device
-
Mike Hibler authored
with ugly "undefined variable" messages in the log. Futureproof the initialization.
-
- 06 Oct, 2005 1 commit
-
-
Kirk Webb authored
Remove the RHL90-specific delaysetup script. It's now common, existing only in the 'linux' subdir.
-
- 04 Oct, 2005 1 commit
-
-
Mike Hibler authored
-
- 03 Oct, 2005 3 commits
-
-
Russ Fish authored
-
Russ Fish authored
-
Mike Hibler authored
-
- 28 Sep, 2005 2 commits
-
-
Leigh B. Stoller authored
-
Kirk Webb authored
Added delaysetup with fixed paths for RHL90
-
- 26 Sep, 2005 1 commit
-
-
Russ Fish authored
-
- 22 Sep, 2005 1 commit
-
-
Russ Fish authored
-
- 21 Sep, 2005 2 commits
- 20 Sep, 2005 1 commit
-
-
Mike Hibler authored
-
- 19 Sep, 2005 3 commits
-
-
Mike Hibler authored
in FreeBSD 5. Whatever slice you want to apply the DIOCSMBR to, has to be open RW.
-
Mike Hibler authored
(5.4 requires a different emulab-fs package due to some dangling shared library reference). It was easier to build a new package than to track down the dependency (and you know how easy building a new package is!)
-
Leigh B. Stoller authored
-
- 16 Sep, 2005 1 commit
-
-
Russ Fish authored
-
- 14 Sep, 2005 1 commit
-
-
Mike Hibler authored
Entailed new instructions for manual setup as well as integration into elabinelab framework. First, the manual path: setup.txt, setup-boss.txt, setup-ops.txt and new setup-fs.txt: Updated to reflect potential for separate fs node. The org here is a little dicey and could be confusing with ops+fs vs. ops and fs. Has not been field tested yet. */GNUmakefile.in: new fs-install target. configure, configure.in, defs-*: Somewhat unrelated, make min uid/gid to use be a defs setting. Also add config of fs-install.in script. boss-install.in, ops-install.in and new fs-install.in: Handle distinct fs node. If you have one, fs-install is run before ops-install. All scripts rely on the defs file settings of FSNODE and USERNODE to determine if the fs node is seperate. utils/checkquota.in: Just return "ok" if quotas are not used (i.e., if defs file FS_WITH_QUOTA string is null. install/ports/emulab-fs: Meta port for fs node specific stuff. Also a patch for the samba port Makefile so it doesn't drag in CUPs, etc. Note that the current samba port Makefile has this change, I am just backporting to our version. Elabinelab specific changes: elabinelab-withfs.ns: NS fragment used in conjunction with tb-elab-in-elab-topology "withfs" to setup inner-elab with fs node. elabinelab.ns: The hard work on the boss side. Recognize seperate-fs config and handle running of rc.mkelab on that node. fs setup happens before ops setup. rc.mkelab: The hard work on the client side. Recognize FsNode setup as well as differentiate ops+fs from ops setup. Related stuff either not part of the repo or checked in previously: emulab-fs package
-
- 13 Sep, 2005 1 commit
-
-
Mike Hibler authored
-
- 12 Sep, 2005 2 commits
- 08 Sep, 2005 1 commit
-
-
Mike Hibler authored
-
- 07 Sep, 2005 1 commit
-
-
Mike Hibler authored
'boss' -> 'boss+router' 'ops' -> 'ops+fs' 'fs' (new role) 'router' (new role) These are in preparation for allowing configurations with split ops and fs nodes (and sometime down the road, split boss and router nodes). This checkin is just the DB state changes along with the scripts that look at that state. The Big One, which actually sets up separate nodes automatically, is undergoing more testing but will be Coming Soon.
-
- 01 Sep, 2005 3 commits
- 30 Aug, 2005 1 commit
-
-
Mike Hibler authored
but "prepare" is the script that goes in the tftpboot directory on boss.
-
- 29 Aug, 2005 3 commits
-
-
Russ Fish authored
-
Russ Fish authored
-
Mike Hibler authored
If unlink fails, do chflags and try again.
-
- 24 Aug, 2005 1 commit
-
-
Russ Fish authored
-
- 22 Aug, 2005 2 commits
- 19 Aug, 2005 3 commits
-
-
Timothy Stack authored
Bring linktest in line with the new event system world order and do some generic cleanup. I'm pretty sure I broke backwards compatibility with old disk images though... * configure, configure.in: Remove linktest.h.in from the list of template files. * event/linktest/GNUmakefile.in: Don't make subdirectories for executables since it can mess up the dependencies. Don't install tb_compat.tcl stuff anymore. Check for '/usr/local/bin/pathrate' and friends, and print out a warning if they are not found. Make a version file for the linktest daemon. * event/linktest/linktest.c: Only subscribe to the events we care about 'STOP/KILL'. Subscribe to TIME START events and kill any linktests that are in progress. Send events through the local elvind instead of running tevc. * event/linktest/linktest.pl.in: Don't run the modified NS anymore to generate the topology file, use gentopofile to do that. Send COMPLETE events to indicate that the tests were finished instead of STOP so it works with event-sequences. Use emulab-sync to report errors between linktest daemons. In addition to sending REPORT events, send LOG events to the SIMULATOR agent so the messages end up in the report e-mail. Fix wait_all so it collects child processes immediately and doesn't leave zombies lying around. Make the static route test work with topologies that aren't fully connected. Change ownership of the linktest error files from root to the swapper. Bump latency tolerance up to 2.5ms. * event/linktest/ltevent.c: Use event_schedule instead of event_notify so the events go through the scheduler. * event/linktest/run_linktest.pl.in: Wait for COMPLETE events insetad of STOPs. * event/linktest/linktest.h.in: Removed. * event/sched/error-record.c: Include linktest error output in the report e-mail. * event/sched/event-sched.c: Linktest now sends COMPLETE events for START events. * tbsetup/gentopofile.in, tmcd/common/config/rc.topomap: Piggy back the generation and management of the linktest config file onto the generation of the topomap. * tbsetup/ns2ir/sim.tcl.in: Add "linktest" event to the Simulator object that runs linktest at level 3 (latency, static routing, and loss). * tmcd/common/libsetup.pm: Add TMLTMAP constant that contains the path to the node local linktest config file. * tmcd/common/rc.linktest: Pass '-u' option to the linktest daemon so it knows what user should to change ownership of files to. * tmcd/freebsd/jail/mkjail.pl: Copy the linktest config file (ltmap) into the jail.
-
Mike Hibler authored
for the server to reboot us. This avoids a race condition that occurs under load (see the comment in the code).
-
Mike Hibler authored
the 'one-true-awk' version of awk, botches the calculations when the values get close to MAXINT. Instead, just create a hex string since sysctl knows about hex numbers.
-