Are there testbed-specific daemons that could interfere with my experiment?
Probably not. By default, the testbed startup scripts currently start two daemons in addition to the OS’s standard set. Other daemons may be started depending on the network services you ask for in your ns file (see below). Unconditionally started daemons: • healthd – A low overhead hardware health monitor. This deamon periodically polls the machine’s health monitoring hardware and sends this information back to our boss node for analysis. The hardware is polled once per second, and a status datagram is sent out once every five minutes. Healthd’s overhead is quite low, but it can be safely killed and disabled from startup if you’re worried about possible side effects. It is started by /etc/testbed/rc.healthd. • slothd – A low overhead usage analysis tool. Slothd is important to efficient testbed utilization and should run on every node whenever possible. Its overhead is almost negligible (essentially less than running ‘ls -l /dev’ once every five minutes), and should not interfere with
