Feature #80

Flush logs when server stops

Added by Lionel Martin over 11 years ago. Updated about 11 years ago.

Status:ResolvedStart date:11/16/2012
Priority:NormalDue date:
Assignee:Pierre Marc% Done:

100%

Category:Application PlatformEstimated time:4.00 hours
Target version:4.7.006
Operating System:Any Tested:Yes
Version:4.7.005

Description

When Nirva stops, and if it hangs for any reason (problem on a service, or whatever), the SYSTEM log does not contain the last bit of information because the logs are not flushed.

Could it be possible to force log flush when Nirva stops, so we are sure we have the latests logs if Nirva hangs or crash ?

I also have another request less important: regarding services, the server logs "Unloading services...", but does not log the trace of the services unloaded, so we can not know which service hangs if one does. Would it be possible to log additional lines for every service unloaded like "Unloading service AA...", so we know which service causes the hang ?

Thanks

History

#1 Updated by Pierre Marc about 11 years ago

  • Assignee set to Pierre Marc
  • Category set to Application Platform
  • Status changed from New to Resolved
  • Tested changed from No to Yes
  • % Done changed from 0 to 100
  • Estimated time set to 4.00

Done in Nirva v 4.7.006

#2 Updated by Pierre Marc about 11 years ago

  • Target version set to 4.7.006

Also available in: Atom PDF