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

Xinetd #29699

Closed
wants to merge 1 commit into from
Closed

Xinetd #29699

wants to merge 1 commit into from

Conversation

fare
Copy link
Contributor

@fare fare commented Sep 23, 2017

Motivation for this change

xinetd has internal services that some legacy software uses, and that I enable at home.

Things done

I actually tested my renaming xinetd to MYxinetd and importing using imports in my configuration.nix.

  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • 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 nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@mention-bot
Copy link

@fare, thanks for your PR! By analyzing the history of the files in this pull request, we identified @Mic92, @7c6f434c and @thoughtpolice to be potential reviewers.

@fare
Copy link
Contributor Author

fare commented Sep 23, 2017

Sorry, my initial push contained updates to gambit and gerbil that are not to be included in this PR (waiting for gambit release to push something stable). I pushed --force an update with just the xinetd updates.

@peterhoeg
Copy link
Member

There's a lot of raw text in there - I suggest creating a function that generates the text for the services instead.

Copy link
Member

@matthewbauer matthewbauer left a comment

Choose a reason for hiding this comment

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

See @peterhoeg's comments

@fare
Copy link
Contributor Author

fare commented Apr 22, 2018

Yes, I need to address these issues indeed.

@7c6f434c
Copy link
Member

(triage) should this be closed until someone has time to do the refactoring?

@fare
Copy link
Contributor Author

fare commented Nov 22, 2018

Closing for now. I will reopen later, if I find time to work on it again...

@fare fare closed this Nov 22, 2018
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

6 participants