Ctrl-Z (the suspend signal) is honored by YottaDB processes in all cases. Previously, if the signal was delivered while the process was executing a section of code where it was not safe to suspend it, the signal was ignored and the user had to retry the Ctrl-Z. Note that as handling the signal is deferred when the process is in sensitive areas of code, it is possible for the response to be momentarily delayed. (#215)
Description
Ctrl-Z of a YottaDB process is normally honored by suspending the process. But if the process is executing some critical section of the code where it cannot be interrupted (for example if the process is allocation memory or displaying the the YDB> or MUPIP> or LKE> prompt etc.) , and the Ctrl-Z comes in during that time window, the Ctrl-Z is currently ignored. This is undesirable.
It is okay to defer suspending the process until the process leaves the critical code section but the suspend should take effect soon after.
Draft Release Note
Ctrl-Z is honored by YottaDB processes in all cases. Previously, if the Ctrl-Z came in while the process is executing some critical section of the code where it cannot be interrupted (for example if the process is allocation memory or displaying the the YDB> or MUPIP> or LKE> prompt etc.), it was ignored and the user had to retry the Ctrl-Z until it worked.
Final Release Note
Ctrl-Z (the suspend signal) is honored by YottaDB processes in all cases. Previously, if the signal was delivered while the process was executing a section of code where it was not safe to suspend it, the signal was ignored and the user had to retry the Ctrl-Z. Note that as handling the signal is deferred when the process is in sensitive areas of code, it is possible for the response to be momentarily delayed. (#215)
Description
Ctrl-Z of a YottaDB process is normally honored by suspending the process. But if the process is executing some critical section of the code where it cannot be interrupted (for example if the process is allocation memory or displaying the the YDB> or MUPIP> or LKE> prompt etc.) , and the Ctrl-Z comes in during that time window, the Ctrl-Z is currently ignored. This is undesirable.
It is okay to defer suspending the process until the process leaves the critical code section but the suspend should take effect soon after.
Draft Release Note
Ctrl-Z is honored by YottaDB processes in all cases. Previously, if the Ctrl-Z came in while the process is executing some critical section of the code where it cannot be interrupted (for example if the process is allocation memory or displaying the the YDB> or MUPIP> or LKE> prompt etc.), it was ignored and the user had to retry the Ctrl-Z until it worked.