The setting: ForceRestartAfterCodeChange
Does not seem to work. The process is not getting killed after an automatic download/install. I have put "immed" in the setting: RestartAfterCodeChange Even though that seems like it shouldn't be necessary. Shouldn't it kill the current process after downloading/installing if "ForceRestartAfterCodeChange" is set? On Tue, Aug 17, 2010 at 1:46 PM, Dan Hulme <[email protected]> wrote: > So the "restart" command implies that the process has already been > killed? I was assuming "restart" had to also stop the current > process. > > On Tue, Aug 17, 2010 at 12:05 PM, Fritz Borgstedt <[email protected]> wrote: >> For Users of ASSP <[email protected]> schreibt: >>> >>>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 >> >> "cd ." would do it. >> >> >> ------------------------------------------------------------------------------ >> 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
