-
Notifications
You must be signed in to change notification settings - Fork 439
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
Recent commit to the BOINC Manager, to not enable stopping the BOINC client when configured as a systemd service, results in anomaly. #5601
Milestone
Comments
original-birdman
changed the title
Recent commit to the BOINC Manager to not enable the stopping BOINC client when configured as a systemd service results in anomaly.
Recent commit to the BOINC Manager, to not enable stopping the BOINC client when configured as a systemd service, results in anomaly.
Apr 25, 2024
AenBleidd
added a commit
to AenBleidd/boinc
that referenced
this issue
May 23, 2024
…a daemon. Remove 'Stop running tasks...' checkbox from the Exit Confirmation dialog on linux when the client is configured to run as a daemon. Small refactoring. This fixes BOINC#5601. Signed-off-by: Vitalii Koshura <[email protected]>
AenBleidd
added a commit
to AenBleidd/boinc
that referenced
this issue
May 23, 2024
…a daemon. Remove 'Stop running tasks...' checkbox from the Exit Confirmation dialog on linux when the client is configured to run as a daemon. Small refactoring. This fixes BOINC#5601. Signed-off-by: Vitalii Koshura <[email protected]>
AenBleidd
added a commit
to AenBleidd/boinc
that referenced
this issue
May 23, 2024
…a daemon. Remove 'Stop running tasks...' checkbox from the Exit Confirmation dialog on linux when the client is configured to run as a daemon. Small refactoring. This fixes BOINC#5601. Signed-off-by: Vitalii Koshura <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The commit is:
82a4fc8
This greys out (disables) the File/Shut down connected client.. option if BOINC is running as a systemd service on the current system.
This works, but produces an anomaly.
I do not think it is working as intended.
It is certainly not working in any logical manner.
The check is done on the local system. However, the same check is used (i.e against the local system) even when the Manager is connected to a remote system.
The result is that when I run the BOINC Manager on my Desktop system (which has BOINC running as a system service) it does not let me stop the client on any system.
However, on my laptop (which isn't running any BOINC client) the option to stop the client is enabled when I connect to any remote system - including that Desktop system (the one where I cannot stop it when logged in locally).
I suspect that the option should always be disabled when connected to a remote system.
And I think there should be an option in the Manager code to enable the "Shut down" option for any connected, logged in client.
The text was updated successfully, but these errors were encountered: