Brutal hackery to ensure that the startcmd (a program object) has a well known name so you can control it via the usual event mechanisms (ns "at" and tevc). Previously, its name came from an internal counter, and because the routine that creates the program object is not at "toplevel", the parser would not rename the object. I'm sure someone who understands this cruft could do better!
Brutal hackery to ensure that the startcmd (a program object) has a
well known name so you can control it via the usual event mechanisms
(ns "at" and tevc). Previously, its name came from an internal
counter, and because the routine that creates the program object is
not at "toplevel", the parser would not rename the object. I'm sure
someone who understands this cruft could do better!

Anyway, now they are named as ${vname}_startcmd.

nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome,nmc-probe/emulab-nome