Session management, especially for Forex (example: Hotspot)

First I have to say sorry, I have really tryed to make it short - but it became longer
Second: Thanks to Steve who patiently answers all the questions (not only mine)

Its all about my problems doing (I think typical) session management with QFJ.

Reffering to my last request "session management at application level" I have additional problems:
Like Steve said its possible to use any external tools or cron jobs, the problem with them is, that they need to be coordinated with the FIX sessions, what is additional (unneccessary) logic.
Now I did this and the following problem occured:
We are running FIX sessions with Hotspot, they are active approx 23 hours per day. In the break of 1 hour we'd like/need to cleanup the system especially we'd like to archive logfiles (approx 700MByte per day).
I did this now using a system functionality (cron), since the two logfiles (event.log and messages.log) were NOT created again from the engine when the new session starts up again we lost a half day of data in the logfiles (database was still written in that period).
Now I assume, that I can not remove the logfiles in a session break, otherwise Im loosing them.
Since I can not find these information in the documentation, its learning by doing ;-(.

My actual conclusion (I might be wrong) is, that when I need to cleanup the system in a session break, I need to restart the entire engine, because otherwise the logfiles are not created.
The problem of session management should be very general for FIX-users, most trading application need some basic functionality:

• run session from start time till end time (while start time could be later than end time, e.g. Forex)
• run session from start day till end day (e.g. sunday till friday)
• do something in the outer session time (e.g. cleaning up the system)
  What I understood, is that actually this is not possible with QFJ, or I was not able to use QFJ correctly at this point.
  The actual solution we are going to implement now is as follows:
  Since we get a logout information (when logout or when disconnect), we implement an own time management logic into our application, what does nothing in case of abnormal disconnect, but cleans up and restarts the engine in case of session break (to recreate the logfiles).

Best regards, Welf