reported by Hussam.

moving the event system interactions into a child process, which
hopefully isolate the cause to either the event system or something
else entirely.

(orphaned) by the protogeni code.

Client-side builds again, but haven't got node to boot correctly.
Need to get pubsubd installed correctly as a service in place of elvind.

to supply the fully specified rspec to both CMs, my changes permit you
to specify only the component_manager_urn for the remote side.

When you start the sliver, the CMs contact each other to resolve the
slice (get the manifest), find the actual node in the manifest, and
resolve that node to get the control network.

This even allows for fully unbound rspecs to be supplied, as long as
the component_manager_urn is specified.

error and no output is provided. Helpful.

Return the manifest when resolving a slice.

Start/Stop methods from its Start/Stop

experiment before it is wiped out for good.

running, so that we do not start multiple times.

silly to do this in long running daemons.

Repeating myself since not everything got committed last time...

In the lastest version of SelfLoader they fixed the taint problem.  It is
literally one line of code (plus updating version string) so I just made
a patch.  Also, fixup boss/ops-install to apply the patch and change the
 default to use the SelfLoader again.

much stuff, not important to keep for so long.

In the lastest version of SelfLoader they fixed the taint problem.  It is
literally one line of code (plus updating version string) so I just made
a patch.  Also, fixup boss/ops-install to apply the patch and change the
default to use the SelfLoader again.

to the GeniRegistry file; move the slice part back into GeniSlice
where it belongs.