-
Notifications
You must be signed in to change notification settings - Fork 27
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-generated clight.service
not respecting --conf-file
#253
Comments
--conf-file
in user *clight.service*clight.service
not respecting --conf-file
Hi @spikespaz ! Sorry for the very late response! Thanks for the very detailed bug report!
Is the file |
Sorry, your reply got lost in "read" notifications for three months.
Nix generates all of these files at generation build time, which I initiate. Programs after subsequent reboots can see all of the depended-on files just as a they would in an orthodox distribution. |
No problem :D It happens to me all the time eheh
Oh, that is weird; can you try to locally build Clight and forcing verbose=true by default? (eg: by adding a line here: |
I'm also using clight on NixOS, but I don't have any problems with the config file getting applied. The only trouble I've had was knowing what changes to make to get the intended result. |
Thank you for your input! I never used NixOS therefore I don't really know what should be done and why. |
If you tell me that this isn't a bug with Clight, but rather with the NixOS module, I will republish on the nixpkgs repository.
Issue Description
TL;DR: Command with
--conf-file
in systemd unit generated by NixOS module starts a service that doesn't respect the provided file, going to default settings. Sometimes.When using the module provided by nixpkgs, enabling the service (plus the geoclue2 location provider) and using the settings attribute provided has no effect (sometimes). The majority of the time Clight appears to use default settings, and changes made to the configuration file (generated through the Nix configuration) have no effect, even when reloaded with
systemctl --user reload clight.service
.Note that only once was I able to get Clight to respect the generated configuration. I can confirm that the systemd units appear to have been correctly generated and enabled; documentation of this will follow. Additionally, the single instance where Clight behaved as expected was not after the initial install, it happened randomly while I was troubleshooting. I do not know what I changed, but it stopped reading my settings again following a system reboot.
Unfortunately, as it seems impossible to configure Clight at the moment, attaching verbose logs is an impossibility.
Environment Specifications
Reproduction
Unknown.
Steps-Taken
I have tried reloading both of the daemons after every ghange, though I believe that this is done by NixOS automatically.
Following are the commands that I have used many times, in many orders, in effort to troubleshoot this myself.
NixOS Module Configuration
NixOS module source: https://github.com/NixOS/nixpkgs/blob/nixos-unstable/nixos/modules/services/x11/clight.nix
Unredacted commitish: spikespaz/dotfiles@a72d561
Generated Configuration File
The configuration file that is generated by Nix can be found with:
Observe that running this ensures that the output file matches exactly what should be visible from the currently-used systemd service unit.
The contents follow:
NixOS-generated systemd Service Units
systemctl --user cat clight.service
systemctl cat clightd.service
The text was updated successfully, but these errors were encountered: