On Aug 21, 2009, at 10:49 AM, Trevor Jacques <[email protected]> wrote:
>> Using launchd solves this, and affords you keeping ASSP startup and >> logging data out of syslog. > > Oops. I forgot that I upgraded to use the watchdog script with Lingon. > Sorry for the confusion. :-/ So you are using the always keep running feature of launchd? Grep your syslog for the name of the launchd item. There is one floating around that sets a user and group which is wrong. See if you can see it triggering a start of ASSP on some crash. Then we can look to find the cause of the crash. While harder to accidentally get two copies or more of ASSP running, that watchdog can make it happen. I was thinking of writing it in a way that if the web admin port was open, launchd could gracefully exit. If the web admin is open, it's running and should not be started again. Maybe I could use the ASSP pid to my advatage, but that may not be cleaned on a crash. -- Scott Iphone says hello. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
