In such cases we probably need a controlled restart at a specific time. I've found a so-called older mutator, but which has not always helped, did not do it because of the load which a server can handle at time. When I took a look at what the precious mutator contains, I think I did not have a second of thought, and I decided to love him a little. Such a mutator seems to work much better as ServerActor than as an ordinary mutator that has another networking deal, the logged lines appear to work very well as an actor not as a mutator. If we consider such a ServerActor, it may have defined a configuration read from an INI file as desired. We define the hour, minute and second required, and the server will stop and restart immediately at a clean stage at that scheduled time + 1 second. We leave this second to observe this activity.
INI file has a simple format - sample below:
Code: Select all
[ServerReset.ServerReset] ResetHour=1 ResetMinute=1 ResetSecond=10