Then a suggestion for the description text: If selected, ASSP will restart itself if it detects a new or changed running script. (AsADaemon <./#AsADaemon>) must be selected and/or AutoRestartCmd <./#AutoRestartCmd> must be non-blank or this setting will have no effect. Leave this field empty to disable the feature. Possible values are 'immed and 1...23' . If set to 'immed', assp will restart within some seconds after a detected code change. If set to '1...23' the restart will be scheduled to that hour. A restart at 00:00 is not supported.
Unless...reading and re-reading this section brings out another point. Even though I'm running on Linux via an external monitoring script, would setting AsAService and leaving AutoRestartCmd blank enable auto-restart? -- Daniel On 07/13/2010 09:13 PM, Thomas Eckardt wrote: >> Is this correct? >> > Yes. > > > > Von: "Daniel L. Miller"<[email protected]> > An: ASSP development mailing list<[email protected]> > Datum: 13.07.2010 21:41 > Betreff: [Assp-test] AutoRestartAfterCodeChange > > > > > I run ASSP on Linux with external supervision (Upstart). So I leave > AsADaemon unchecked, and AutoRestartCmd is blank. > > The descriptive text indicates ASSP will NOT restart under these > conditions. Is this correct? Or should the description be modified? > > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
