1. 14 Nov, 2018 1 commit
  2. 13 Nov, 2018 2 commits
  3. 04 Sep, 2018 1 commit
  4. 17 Aug, 2018 3 commits
  5. 14 Aug, 2018 2 commits
  6. 16 Jul, 2018 1 commit
  7. 03 Jul, 2018 1 commit
  8. 02 Jul, 2018 1 commit
  9. 28 Jun, 2018 1 commit
  10. 26 Jun, 2018 1 commit
  11. 31 May, 2018 1 commit
  12. 28 May, 2018 2 commits
  13. 25 May, 2018 1 commit
  14. 23 Apr, 2018 1 commit
  15. 18 Apr, 2018 1 commit
  16. 27 Feb, 2018 1 commit
  17. 21 Feb, 2018 1 commit
  18. 16 Feb, 2018 3 commits
    • Tomas Krizek's avatar
    • Tomas Krizek's avatar
      systemd: remove kresd.service meta-service · 1f9aa9a6
      Tomas Krizek authored
      The kresd.service meta-service could be confusing for users and provides
      no extra functionality. The system-kresd.slice can be used to restart or
      stop all running instances.
      Distributions shipping with /etc/init.d/kresd should symlink the
      kresd.service to /dev/null to prevent systemd-sysv-generator from
      creating this service.
    • Daniel Kahn Gillmor's avatar
      More systemd service management cleanup · 0398a985
      Daniel Kahn Gillmor authored
      Please see discussion at:
      The new approach is:
       * non-templated kresd.socket and kresd-tls.socket, for the
         public-facing listening ports.  They know to invoke kresd@1.service
         if they're socket-activated.
       * kresd@.service *is* templated, to allow the admin to add more
         concurrent runners with:
            systemctl enable kresd@2.service
       * kresd-control@.socket is still templated, since each daemon has a
         separately-addressable different control port.
       * non-templated kresd.service is a dummy meta-service.  it is in the
         same slice as kresd@.service, and all the kresd@.service instances
         are PartOf= it, so you should be able to stop and restart all
         services together.  On systems like debian that ship
         /etc/init.d/kres, this also avoids having systemd-sysv-generator
         create a kresd.service based on the initscript.
       * no templated instances are explicitly instantiated during initial
         ship, but kresd@1.service should be socket-activated cleanly
      Gbp-Pq: Name 0010-More-systemd-service-management-cleanup.patch
  19. 05 Feb, 2018 1 commit
    • Daniel Kahn Gillmor's avatar
      doc: kresd.systemd belongs in section 7 of the manual · 23c8ffbf
      Daniel Kahn Gillmor authored
      "man man" says that the sections are:
             1   Executable programs or shell commands
             2   System calls (functions provided by the kernel)
             3   Library calls (functions within program libraries)
             4   Special files (usually found in /dev)
             5   File formats and conventions eg /etc/passwd
             6   Games
             7   Miscellaneous  (including  macro  packages  and  conventions), e.g.
                 man(7), groff(7)
             8   System administration commands (usually only for root)
             9   Kernel routines [Non standard]
      Since there is no command named kresd.system it does not belong in
      section 8.
      Section 7 includes conventions and useful patterns like gitcli(7),
      which seems more similar to the documentation that is supplied in
  20. 31 Jan, 2018 2 commits
  21. 30 Jan, 2018 3 commits
    • Tomas Krizek's avatar
      systemd: enable multiple processes with socket activation · 4905226d
      Tomas Krizek authored
      In order to be able to spawn multiple processes with socket activation,
      systemd template (see systemd.unit(5)) is used. This allows the user to
      create any amount of instances by simply providing a unique name for
      each of them. The most sensible instance identifiers are natural
      numbers, but any convention could be used.
      The default recommended service name becomes kresd@1.service, replacing
      the older kresd.service. Sockets are renamed in a similar way. Users are
      able to take advantage of bash expansion to spawn/control multiple
      processes, e.g. "systemctl start kresd@{1..16}.service"
      The socket-activated service can now be launched directly with
      "systemctl start kresd@1.service", which will request the associated
      sockets without the need for any extra priviledges or capabilities.
      Stopping the kresd service now also stops the associated sockets.
      Stopping any individual socket is an isolated opration now (stopping
      kresd@1.socket no longer stop kresd-tls@1.socket and
      Users and packagers are also encouraged to use drop-in files for extra
      configuration or modifications to ensure compatibility with their
    • Vladimír Čunát's avatar
      doc: fixup after moving files around · 975d6605
      Vladimír Čunát authored
    • Tomas Krizek's avatar
      documentation: reorganize chapters · 3635da41
      Tomas Krizek authored
      The manual page discusses basic usage of kresd, but completely lacks
      configuration description. Users are pointed to
      https://knot-resolver.readthedocs.io for reference. When visiting this
      page, the most important information they don't have yet, is how to
      configure kresd. This should be the first chapter in the documentation
      to make it easier to find.
  22. 29 Jan, 2018 1 commit
  23. 25 Jan, 2018 1 commit
  24. 24 Jan, 2018 1 commit
  25. 23 Jan, 2018 3 commits
  26. 12 Jan, 2018 1 commit
    • Marek Vavruša's avatar
      build: support `make lint-c` with clang-tidy · ad213c47
      Marek Vavruša authored
      This supports linting of C code using clang-tidy to fix common
      security and code quality issues early in the development workflow.
      The benefit is that less time has to be spent in code reviews to
      point out obvious problems, and ideally when the outstanding issues
      are fixed, clang-tidy (and clang-format) can also be used to to
      automatically fix basic problems and enforce common code style,
      similarly to `go vet && go fmt` workflow.
  27. 08 Dec, 2017 1 commit
  28. 07 Dec, 2017 1 commit