On 2005年1月28日 16:28:13 -0800, Jared Rhine <jared@xxxxxxxxxxx> wrote:
>> xcs should daemonize itself to prevent this from happening.
>
> Actually, I'd really like an option to keep xend and xensv in the
> foreground (and log to stdout), as I want to run them under runit (like
> daemontools) for XenCD. I haven't gotten there yet, but if anyone
> touches this code, it'd be nice to leave this possibility open in the
> design.
Yes, definitely. Twisted has code for doing daemonization/pidfile management 
that is much more flexible than xend's current approach. I looked into 
refactoring it to use that as well as adding support for Twisted's 
remote-object protocol, but I kept finding things about xend's architecture I 
wanted to change, so I gave up temporarily :) I will probably revisit this 
after finishing my current project, which just talks to xend via its HTTP 
protocol. Basically what needs to be done is to remove entirely the code in 
SrvDaemon that starts things up, and use 'twistd' to start it instead.
Allen
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel