<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.2900.3314" name=GENERATOR></HEAD> <BODY> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>Hi,</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>      As Garret Cooper mentioned earlier, my team at Cisco is thinking of working with Upstart as a process manager.</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>One of the questions that have come up with respect to a client library to control Upstart.</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>There is a need for a process to talk/listen to the UpstartInit process for the following</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>   1. Notifications about the state of a process.</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>   2. Request Upstart to read a new/update job file.</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>   3. Send an event to Upstart to trigger the start of a job.</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>The above functions are part of the upstartctl command, but need to be in a library form that can be linked into another application so that it can interact with Upstart.</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>Now it should be relative;y simply to create client library with some well defined API, and for the most part this already seems to be available in the form of message definitions in the upstart directory. </FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>But they are in GPLv2 licensing. I would suspect such a client library that could be linked to many 3rd party applications needs to be LGPLed instead of GPLed?</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>What are our options here?</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>    We could write/release our own LGPLed client library that talkes to UpstartInit but that  would still need to share some header files and stuff relating to message definitions, error numbers, etc. or duplicating them and trying to keep them in sync.</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>    Are there better options?</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>Thanks,</FONT></SPAN></DIV> <DIV><SPAN class=203080323-11062008><FONT face=Arial size=2>Sarvi</FONT></SPAN></DIV></BODY></HTML>