FAHCore_a7 and _22 don't always sync files on Windows Shutdown.

[bb30994]

When a Windows Shutdown is initiated, all active processes are notified of the pending shutdown and given a period of time to clean up their files. I've noticed that FAHCore_a7 does not process that information correctly. After the wait interval expires, Windows forces the remaining processes to die. This may or may not leave corrupted files (needing a sync process). This increases the probability of a GURU MEDITATION error.

If I manually pause all A7 WUs, the shutdown does not leave corrupted files.

Why can't a7 (or it's wrapper) manage these files correctly when the shutdown warning is issued?

See also https://foldingforum.org/viewtopic.php?f=106&t=32011&p=310002#p310002 and #1289.

January is history. When can we beta-test those pending changes?

[shorttack]

@bb30994 Bruce, is this still an issue with the 7.6 beta? If so, I'll call a defect.

[bb30994]

I got a Guru Meditation error when I shut down 7.4.4 to upgrade. Bye-bye one Gromacs WU, I'll test it again but checkpoints are not a FAHClient issue, it's a FAHCore issue. 0.0.2 has not change (yet).

[bb30994]

I contend that this is a bug, not an enhancement.

Any Windows program should be able to close its files during an orderly shutdown of Windows. When the OS notifies a program that a shutdown is being processed, it waits a bit for programs to close and then rechecks. (If somebody is editing a file, they have long enough to save their file.) Then it's more forceful, and it lists specific programs which are "preventing Windows from shutting down"

The FAHCore has the option of refusing to shut down if it needs longer than the allotted time and then closing itself once the files have been closed.

Being uncooperative with Windows shutdown requests is not the way to write a program.

[bb30994]

This is an issue for FAHCore_A7, not for FAHClient.

[bb30994]

same issue reported here #1458 but in a very different context

[shorttack]

See also #1468, #1436

[bb30994]

The following messages were displayed in a recent log:
19:39:31:WU02:FS01:0x22:Watchdog triggered, requesting soft shutdown down
19:49:30:WU02:FS01:0x22:Watchdog shutdown failed, hard shutdown triggered

Whatever is preventing the soft shutdown request from being honored needs to be examined. The FAHCore should accept that soft shutdown request unless a checkpoint is actively being written. The trigger for the hard shutdown should allow long enough to complete the writing of an active checkpointing process.