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

earlyoom: patch absolute dbus path and make nixos module up to date #88443

Merged
merged 3 commits into from May 25, 2020

Conversation

oxalica
Copy link
Contributor

@oxalica oxalica commented May 20, 2020

Motivation for this change

earlyoom v1.6 replaces old notification logic with dbus-send / systembus-notify. (See Changelog.)
But dbus path is not patched and options of nixos/earlyoom is not up to date.

Related: #88441

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
    • Not changed.
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

description = ''
Send notifications about killed processes via the system d-bus.
To actually see the notifications in your GUI session, you need to have
<literal>systembus-notify</literal> running as your user.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should package this? Opened rfjakob/systembus-notify#3 for a user service

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #88441. But is there any way to setup a systemd user service in system configuration?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It sounds like the autostart desktop file is enough

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(but yes there is, through systemd.user.services I think)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I make environment.systemPackages = [ pkgs.systembus-notify ]; when notification is enabled? But this requires #88441 to be merged first.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah - let’s do that and merge systembus-notify first

@oxalica oxalica requested a review from matthewbauer May 25, 2020 14:59
@matthewbauer matthewbauer merged commit fe3e52c into NixOS:master May 25, 2020
@oxalica oxalica deleted the fix/earlyoom branch May 25, 2020 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants