Do you think we could have done something in the ActiveMQ startup scripts to protect against even odd environments like the one you encountered?
On Thu, May 3, 2012 at 12:43 AM, justintime <[email protected]> wrote: > My apologies, it's something on the system, not in the code. That'll teach > me to post before checking source. I'll post the fix once I find it for > anyone else that might come across it. > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/World-writable-KahaDB-files-tp4603663p4605121.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- ** *Hiram Chirino* *Software Fellow | FuseSource Corp.* *[email protected] | fusesource.com* *skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino> * *blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>* * * * *
