CA-413319: Ensure console timeout reflect real status in db

[LunfanZhang]

For the following scenarios, console timeout may not work and not reflect the real status of the database:

• XenServer upgrade to a new version(e.g., XS9)
• User accidentally deletes the configuration file

Add checks to ensure database and real status are matched, when the check detect the config file is lost and the config in db is not non-zero number, then it will re-create the configure file again.

[lindig]

My understanding of the code is that the config file is re-created with the value from the database. This is not obvious from how this is presented in the commit message and discussion here. The code looks like it takes a value from the database and then again writes it to the database. But in addition if creates a file.

[LunfanZhang]

My understanding of the code is that the config file is re-created with the value from the database. This is not obvious from how this is presented in the commit message and discussion here. The code looks like it takes a value from the database and then again writes it to the database. But in addition if creates a file.

Yes, your understanding is absolutely correct. If the config file is lost, the system will detect a mismatch between the configuration in the database and the running system, especially after an upgrade that removes the config file or if a user accidentally deletes it. Therefore, a protection check is being added here.
I updated the PR message a bit to clarify this.