Skip to content
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

Fix: DaemonUsername check on QNAP #391

Merged
merged 1 commit into from
Sep 13, 2024
Merged

Conversation

dnzbk
Copy link
Collaborator

@dnzbk dnzbk commented Sep 13, 2024

Description

  • added additional check for DaemonUsername if it's equal to "root" for Backward compatibility with QNAP which doesn't have a "root" user, but for historical reasons in nzbget.conf we use "root" as the default value in DaemonUsername which causes problems when running nzbget as a daemon on QNAP.

Testing

  • Linux Debian 12

@dnzbk dnzbk requested review from phnzb and luckedea September 13, 2024 14:19
@dnzbk dnzbk linked an issue Sep 13, 2024 that may be closed by this pull request
1 task
@dnzbk dnzbk merged commit 2dc6755 into develop Sep 13, 2024
1 check passed
@dnzbk dnzbk deleted the fix/daemon-username-on-qnap branch September 13, 2024 14:31
beertje44 pushed a commit to beertje44/nzbget that referenced this pull request Dec 4, 2024
- added additional check for DaemonUsername if it's equal to "root" for Backward compatibility with QNAP which doesn't have a "root" user, but for historical reasons in nzbget.conf we use "root" as the default value in DaemonUsername which causes problems when running nzbget as a daemon on QNAP
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

QNAP: unable to start daemon "invalid DaemonUsername"
2 participants