On Jun 10, 2010, at 4:22 AM, "GrayHat" <[email protected]> wrote:
> >> Sorry, hit send accidentally. It seems like assp is designed so that >> only a start command makes sense in AutoRestartCmd, but perhaps >> there's a point to including kill and pid-removal stages as well? > > imHo yes; I mean, a restart script should take care of stopping assp, > waiting for it to completely stop (for a reasonable amount of time) go > on killing the process (if still alive), delete the "pid" file and > then > go > on starting ASSP again; I did that on windows using some "tools" > and it should be even easier on unix/linux; The default debian script has this functionality, that's no issue. What I'm saying is that, by the time AutoRestartCmd is triggered, the assp process is no longer running. If a kill step is included it just generates an error that there is nothing to kill, at least on Linux. There seems to be an entire stage of cleanly ending assp processes that occurs before AutoRestartCmd even enters the picture. So I'm no sure there's any point in trying to duplicate that. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
