I finally got around to checking, and LOG EVENT is not a thread-safe command. Pity! It would be very handy if this command were usable from a preemptive process as it would give us a great way to stream log data out to the system for collection by an "agentless" (cough-cough) tool like Loggly.
Given the open bug that prevents me from rolling log files safely, I've got to use memory-based solutions to get logs out of 4D. Since LOG EVENT isn't usable preemptively, I'm down to HTTP Get/Request pushing data over HTTP to the Loggly API. Not ideal, but that's the only thing that I can figure that's even workable from a preemptive process at the moment. If anyone else cares and agrees, would you mind posting a feature request on the Forums to make LOG EVENT thread-safe? Or, if not, to tell us definitively that LOG EVENT falls into the too hard basket. If I'm never going to get a feature, it's better to know sooner rather than later. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
