-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
nixos/ddclient: make nsupdate protocol usuable #154124
Conversation
@@ -29,8 +29,10 @@ let | |||
configFile = if (cfg.configFile != null) then cfg.configFile else configFile'; | |||
|
|||
preStart = '' | |||
install ${configFile} /run/${RuntimeDirectory}/ddclient.conf | |||
${lib.optionalString (cfg.configFile == null) (if (cfg.passwordFile != null) then '' | |||
install --owner ddclient -m600 ${configFile} /run/${RuntimeDirectory}/ddclient.conf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This mainly avoids warnings but should have not be strictly necessary.
Can you fix the manual? |
fixed. |
Can everyone please stop breaking this module without testing it? This is the exact same problem as last time.
It's a |
I tested this module. The reverted commit did not change the owner to ddclient as well, which is what was done here.
This is true not in general. If it cannot find the user than something is wrong with your nss setup. Systemd creates this user before starting |
In 1024571 I fixed some race conditions that broke dynamic user in some cases. What is the full restart log, when you run an upgrade? |
Thanks for the hint, I'll look into that. I'd been trying to look for documentation on how
Possibly! It certainly broke a switch :(
I can try to look into it in a bit but if it indeed is related to nscd updating at the same time, I've already performed the update by now >< EDIT: does that mean units using dynamicuser need an |
It looks like my nscd fix is no longer in nixpkgs. I re-introduced it in this PR: #154928 |
just FYI so that you know: I am the more or less the upstream (core) maintainer of ddclient as of yesterday. |
dual-stack support please :) |
wasn't that added some time ago? I'm pretty sure it's working for me. |
Ok. Configuration was not clear to me at all. I saw something that looked like an RFC. Might be also that the nsupdate backend does not handle this. |
ddclient/ddclient@24ba945 appears to be the result of that and the introduction of proper support, but there hasn't been a tagged release in 2 years, so...
Maybe yeah, I'm not sure what support for it looks like for individual backends :< |
is there a workaround on nixpkgs-unstable (eg without #154928) to get ddclient working again? |
Write me a private message and we can figure this out.
In the meantime I created a fork which I am planning to upstream in the next weeks and then create an RC maybe in a month or so. No promises though. |
Motivation for this change
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes