-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting preference maybe rollback when execute multiple targetcli requests concurrently #188
Comments
zoumingzhe
added a commit
to zoumingzhe/configshell-fb
that referenced
this issue
Oct 22, 2021
Setting preference maybe rollback when execute multiple targetcli requests concurrently. Please see open-iscsi/targetcli-fb#188 for details. In order to solve this problem we must first initialize a Console object. Signed-off-by: Zou Mingzhe <[email protected]>
zoumingzhe
added a commit
to zoumingzhe/configshell-fb
that referenced
this issue
Oct 22, 2021
Setting preference maybe rollback when execute multiple targetcli requests concurrently. Please see open-iscsi/targetcli-fb#188 for details. In order to solve this problem we must first initialize a Console object. Signed-off-by: Zou Mingzhe <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ConfigShell always initialization new Console object.
However, the lockfile need to be opened before requesting flock.
At this time, an exception may occur and need to be output to the console.
Currently, ConfigShell always initializes a new Console object.
So, ConfigShell is initialized first to be able to print information.
The prefs.bin file will be loaded when ConfigShell is initialized.
In this case, the old value may be read, if a new preference is being set and not saved.
Even worse, if this is also a setting command, the previous setting will be rolled back.
The text was updated successfully, but these errors were encountered: