- Aug 26, 2016
-
-
Jonathan Boulle authored
sdjournal: fix concurrent map access
-
- Aug 25, 2016
-
-
Alexander Menzhinsky authored
libsystemdFunctions is shared between Journal instances than may cause concurrency issues accessing the same functions at the same time for the very first time
-
Luca Bruno authored
sdjournal: fix race condition in test
-
- Aug 24, 2016
-
-
Alexander Menzhinsky authored
since the go builtin command creates a closure, it uses the same err variable than causes race condition in tests
-
Jonathan Boulle authored
sdjournal: free correct pointer
-
- Aug 23, 2016
-
-
Jonathan Boulle authored
-
Jonathan Boulle authored
Since defer creates a closure, it ends up freeing the wrong pointer in these situations (i.e. not the one that ends up getting allocated by asprintf during the actual sdjournal call).
-
Luca Bruno authored
sdjournal: fix memory leak in cursor handling
-
Alexander Menzhinsky authored
free memory that's allocated by the sd_journal_get_cursor function bugfix
-
- Aug 17, 2016
-
-
Jonathan Boulle authored
activation: don't specify NextProtos so that we can take advantage of HTTP/2
-
Aaron Wood authored
-
- Aug 15, 2016
-
-
Jonathan Boulle authored
util: fix import path
-
Gyu-Ho Lee authored
-
Luca Bruno authored
dbus: add PropPids to set initial pids of transient scope units
-
Luca Bruno authored
util: conditionally build CGO functions
-
Anthony Romano authored
Some projects don't need the CGO functions in the util package; split out the functions into a separate file so CGO_ENABLED=0 works if those functions are never used. Fixes #171
-
- Jul 28, 2016
-
-
Luca Bruno authored
dbus: add mask/unmask for unit files
-
- Jul 26, 2016
-
-
Jean Kahrs authored
-
- Jul 20, 2016
-
-
Luca Bruno authored
daemon: improve SdNotify errors signaling
-
- Jul 19, 2016
-
-
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
-
- Jul 14, 2016
-
-
Michael Gebetsroither authored
-
- Jul 13, 2016
-
-
Luca Bruno authored
sdjournal: add GetDataBytes() and GetDataValueBytes() to Journal
-
Gregory Petrosyan authored
This allows to avoid extra string → []byte conversion overhead for cases when journal field value is e.g. parsed (which usually requires []byte).
-
- Jul 12, 2016
-
-
Luca Bruno authored
sdjournal: fix a race in GetEntry test
-
- Jul 05, 2016
-
-
Luca Bruno authored
travis: run whole testsuite in containers
-
Luca Bruno authored
dbus: fix testsuite
-
Jonathan Boulle authored
sdjournal: fix an implicit seek to head
-
- Jul 04, 2016
-
-
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.
-
- Jul 02, 2016
-
-
Luca Bruno authored
Some assumptions do not hold anymore on recent debian-derivatives. Tests updated to avoid failures in modern dbus/systemd environments.
-
- Jun 28, 2016
-
-
Luca Bruno authored
-
- Jun 21, 2016
-
-
Jonathan Boulle authored
sdjournal: add test for incorrect Read() length
-
Luca Bruno authored
-
- Jun 20, 2016
-
-
Luca Bruno authored
sdjournal: fix incomplete reads in JournalReader.Read()
-
Luca Bruno authored
Rework configuration to run testsuite into containerized environments. This allows to run all tests on travis.
-
Luca Bruno authored
Hard-sleep instead of waiting for a journal event. This fixes a race due to waiting for any events but enumerating only matching ones.
-
- Jun 17, 2016
-
-
Jonathan Boulle authored
sdjournal: fix Writer call
-
Jonathan Boulle authored
-
- Jun 14, 2016
-
-
Jonathan Boulle authored
sdjournal: Break the loop if error happens during Write().
-
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
-
- Jun 13, 2016
-
-
Yifan Gu authored
-