Skip to content
Snippets Groups Projects
  1. Aug 26, 2016
  2. Aug 25, 2016
  3. Aug 24, 2016
  4. Aug 23, 2016
  5. Aug 17, 2016
  6. Aug 15, 2016
  7. Jul 28, 2016
  8. Jul 26, 2016
  9. Jul 20, 2016
  10. Jul 19, 2016
    • Alessandro Puccetti's avatar
      SdNotify: return value compliant to sd_notify() · 0d7fccc1
      Alessandro Puccetti authored
      After this patch, SdNotify returns values compliant to sd_notify(3).
      
      Return values:
      * (false, nil) - notification not supported
      * (false, err) - notification supported, but failure happened
      * (true, nil) - notification supported, data has been sent
      0d7fccc1
  11. Jul 14, 2016
  12. Jul 13, 2016
  13. Jul 12, 2016
  14. Jul 05, 2016
  15. Jul 04, 2016
    • Luca Bruno's avatar
      sdjournal: fix an implicit seek to head · 17c63298
      Luca Bruno authored
      When a JournalReader is initialized with a NumFromTail bigger than
      the number of available entries, cursor will be positioned on the
      first entry. Upon initial (mandatory) Next invocation, it will
      incorrectly start reading from the second entry.
      
      This fixes a pathological case where the first entry of a journal
      is always ignored when using NumFromTail.
      17c63298
  16. Jul 02, 2016
    • Luca Bruno's avatar
      dbus: fix testsuite · 4b1e7353
      Luca Bruno authored
      Some assumptions do not hold anymore on recent debian-derivatives.
      Tests updated to avoid failures in modern dbus/systemd environments.
      4b1e7353
  17. Jun 28, 2016
  18. Jun 21, 2016
  19. Jun 20, 2016
  20. Jun 17, 2016
  21. Jun 14, 2016
    • Jonathan Boulle's avatar
      Merge pull request #174 from yifan-gu/fix_follow · e8339e7d
      Jonathan Boulle authored
      sdjournal: Break the loop if error happens during Write().
      e8339e7d
    • Alban Crequy's avatar
      JournalReader: fixes in JournalReader.Read() · 6ffde06f
      Alban Crequy authored
      This patch fixes two issues in JournalReader.Read():
      
      1. The return value of copy() was ignored and JournalReader.Read() was
      returning the wrong amount of bytes copied.
      
      2. JournalReader implements the Reader interface so it must be able to read a
      specific amount of bytes. Journald on the other hand only allows us to read
      full entries of arbitrary size (without byte granularity). JournalReader
      therefore needs to internally buffer entries that don't fit in the read buffer.
      Callers should keep calling until 0 and/or an error is returned.
      
      Fixes https://github.com/coreos/go-systemd/issues/172
      6ffde06f
  22. Jun 13, 2016
Loading