I can't comment on the output buffering, but the current versions of 
ASSP do have support for autorestart when supervised externally.
-- 
Daniel


On 8/17/2010 10:17 AM, Dan Hulme wrote:
> Every time I download the latest ASSP, I make a small mod to force the
> output to flush.  Basically, I add the line "$|=1" somewhere at the
> beginning of the code.  The reason for this is that output buffering does
> not play nicely with log managers like multilog from daemontools.
>
> If there were just an option to force output buffering to be turned off,
> that would allow me to update assp without having to modify it every time.
> Any way to do this, or a chance of it being added?
>
> Another nice feature for daemontools would be a way to tell assp that the
> "autorestart" command is just to exit.  Since daemontools will automatically
> restart assp, that's all that would be needed for a restart.  Currently I am
> using:
>
> /bin/kill `cat /daemon/assp/root/pid`
>
> Kind of silly, but it works.
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Assp-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/assp-user


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to