Hello,
My name is Garrett Cooper and one of the groups I'm a part of at
Cisco is in charge of finding a process management tool in the IOS ->
Linux porting project currently in place. upstart is an excellent
candidate for this work.
Due to legalize we're in limbo right now awaiting the AOK to
import upstart into our SCM. However, we're still doing research tasks
trying to determine what, if any features are missing, how should the
code be tested, and how can we contribute any non-Cisco specific
improvements back to the upstart community.
A few feature questions, first off:
>From README:
"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,
-Garrett
--
upstart-devel mailing list
upstart-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/upstart-devel
