No subject

Tue Apr 29 15:47:36 BST 2008

  "supervising them while the system is running."

      What method is used to monitor processes? Does upstart stay
resident in memory checking to ensure that all forked processes are
healthy, or does it poll attached PID data, etc?

  " * events may also be generated at timed intervals, or when files
are changed (not yet implemented);"

      What exactly is meant by the term "events"? Is that an
abstraction for cases where process(es) die / become defunct or where
soft / hard deadlines are established for action to take place with a
specific process or set of processes?

      Is the initd literally replaced by a copy developed by the
upstart group, or has this been moved over from sysv (a little bit?)?

About testing:
      Currently the code is organized into one large C-file with what
appears to be whitebox only tests of the APIs. Has some thought been
put into how, if at all possible, it is to generate black box tests as
well for the code?

      Has anyone considered reorganizing the test code or adding
additional tests to upstart?

Thanks and I look forward to your reply,

More information about the upstart-devel mailing list