I haven't but that is a good idea that I'll look into after the first of the year.
Also, due to the large request volume when these scans run I was thinking about something like this: Log each request in an individual file, and save a reference to it. When the request is finished delete the file. That would (hopefully) only leave the problematic requests on disk for review. Otherwise I'll have thousands of requests to mine through. For now I'm trying to get some tools in place so that the non-admin types here can respond to unexpected system problems over the holidays. I'll be traveling and won't be available to immediately respond. Also, I'm probably going to have to run an Applescript to quit 4D. The user that 4D runs under can't run killall (even with sudoers modifications) I'll just change the script to path/to/osascript kill4D.app and use something similar to what Steve Alex provided. Thanks, -- Brad On 12/12/11 11:29 AM, "Aparajita Fishman" <[email protected]> wrote: >You you tried logging requests that NTP passes to Active4D to find out if >NTP or Active4D is the one choking on them? > >Regards, > > Aparajita > >_______________________________________________ >Active4D-dev mailing list >[email protected] >http://list.aparajitaworld.com/listinfo/active4d-dev >Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/ _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/
