by cjnaz » Mon Mar 10, 2025 1:07 am
Thank you for your reply. Sorry, I don't follow your example.
"Please List me #$@%$&%&#@* all ^$@#*#^$ test @#*&@^#$** and delete %$#@!^&%# all @&^%*$#@*&^#$@*&^ files from ^&%$#@&#^%$@&^ RHEL9 Host"
I think you're suggesting that after a sleep MM cannot determine if it has a correct connection to the the .DB file, and therefore it could blissfully do damage. Clearly, based on the endless loop of error messages, MM
can determine that it has not successfully reconnected the .DB file. To the best of my (user) knowledge, MM is not doing anything when the machine goes to sleep. It would be reasonable to terminate any in-process operations when recovering from sleep, and tell the user that operations were aborted.
I'm saying that MM
should be able to correctly reconnect to the .DB file, just as easily as when the application is started. Currently, I have to kill MM via the task manager and then it will start just fine. I deal with no other application that cannot recover from sleep wake-up or a network loss/recovery on Windows or Linux. That's a bug.
At a minimum, it should show the error and give options for terminate or restart, if it cannot successfully recover from sleep.
regards,
cjn
Thank you for your reply. Sorry, I don't follow your example.
[quote] "Please List me #$@%$&%&#@* all ^$@#*#^$ test @#*&@^#$** and delete %$#@!^&%# all @&^%*$#@*&^#$@*&^ files from ^&%$#@&#^%$@&^ RHEL9 Host"[/quote]
I think you're suggesting that after a sleep MM cannot determine if it has a correct connection to the the .DB file, and therefore it could blissfully do damage. Clearly, based on the endless loop of error messages, MM [i]can [/i]determine that it has not successfully reconnected the .DB file. To the best of my (user) knowledge, MM is not doing anything when the machine goes to sleep. It would be reasonable to terminate any in-process operations when recovering from sleep, and tell the user that operations were aborted.
I'm saying that MM [i]should [/i]be able to correctly reconnect to the .DB file, just as easily as when the application is started. Currently, I have to kill MM via the task manager and then it will start just fine. I deal with no other application that cannot recover from sleep wake-up or a network loss/recovery on Windows or Linux. That's a bug.
At a minimum, it should show the error and give options for terminate or restart, if it cannot successfully recover from sleep.
regards,
cjn