summaryrefslogtreecommitdiff
path: root/src/journal
Commit message (Collapse)AuthorAge
...
* journald: turn ForwardToSyslog= off by defaultLennart Poettering2014-07-11
| | | | | After all, rsyslog and friends nowadays read their data directly from the journal, hence the forwarding is unnecessary in most cases.
* journal/compress: improve xz compression performanceJon Severinsson2014-07-08
| | | | | | | | | | | | | | | | | | | | | | | | The new lzma2 compression options at the top of compress_blob_xz are equivalent to using preset "0", exept for using a 1 MiB dictionary (the same as preset "1"). This makes the memory usage at most 7.5 MiB in the compressor, and 1 MiB in the decompressor, instead of the previous 92 MiB in the compressor and 8 MiB in the decompressor. According to test-compress-benchmark this commit makes XZ compression 20 times faster, with no increase in compressed data size. Using more realistic test data (an ELF binary rather than repeating ASCII letters 'a' through 'z' in order) it only provides a factor 10 speedup, and at a cost if a 10% increase in compressed data size. But that is still a worthwhile trade-off. According to test-compress-benchmark XZ compression is still 25 times slower than LZ4, but the compressed data is one eighth the size. Using more realistic test data XZ compression is only 18 times slower than LZ4, and the compressed data is only one quarter the size. $ ./test-compress-benchmark XZ: compressed & decompressed 2535300963 bytes in 42.30s (57.15MiB/s), mean compresion 99.95%, skipped 3570 bytes LZ4: compressed & decompressed 2535303543 bytes in 1.60s (1510.60MiB/s), mean compresion 99.60%, skipped 990 bytes
* fix #ifdefRonny Chevalier2014-07-08
|
* journal/compress: fix calls to decompress_blobZbigniew Jędrzejewski-Szmek2014-07-07
|
* coredumpctl: show a useful error on permission problemsZbigniew Jędrzejewski-Szmek2014-07-06
|
* compress: add benchmark-style testZbigniew Jędrzejewski-Szmek2014-07-06
| | | | | | | | | | | | | | | | | | | This is useful to test the behaviour of the compressor for various buffer sizes. Time is limited to a minute per compression, since otherwise, when LZ4 takes more than a second which is necessary to reduce the noise, XZ takes more than 10 minutes. % build/test-compress-benchmark (without time limit) XZ: compressed & decompressed 2535300963 bytes in 794.57s (3.04MiB/s), mean compresion 99.95%, skipped 3570 bytes LZ4: compressed & decompressed 2535303543 bytes in 1.56s (1550.07MiB/s), mean compresion 99.60%, skipped 990 bytes % build/test-compress-benchmark (with time limit) XZ: compressed & decompressed 174321481 bytes in 60.02s (2.77MiB/s), mean compresion 99.76%, skipped 3570 bytes LZ4: compressed & decompressed 2535303543 bytes in 1.63s (1480.83MiB/s), mean compresion 99.60%, skipped 990 bytes It appears that there's a bug in lzma_end where it leaks 32 bytes.
* journal: add LZ4 as optional compressorZbigniew Jędrzejewski-Szmek2014-07-06
| | | | | | | | | | | | | | Add liblz4 as an optional dependency when requested with --enable-lz4, and use it in preference to liblzma for journal blob and coredump compression. To retain backwards compatibility, XZ is used to decompress old blobs. Things will function correctly only with lz4-119. Based on the benchmarks found on the web, lz4 seems to be the best choice for "quick" compressors atm. For pkg-config status, see http://code.google.com/p/lz4/issues/detail?id=135.
* journal/compress: return early in uncompress_startswithZbigniew Jędrzejewski-Szmek2014-07-06
| | | | | | | uncompress_startswith would always decode the whole stream, even if it did not start with the given prefix. Reallocation policy was also strange.
* coredump: vacuum - fix calculation of 10% of fs size for MaxUseThomas Hindoe Paaboel Andersen2014-07-01
|
* journald: make MaxFileSec really default to 1monthMichał Bartoszkiewicz2014-06-27
| | | | | journald.conf(5) states that the default for MaxFileSec is one month, but the code didn't respect that.
* coredump: simplify compression logic a bitLennart Poettering2014-06-27
| | | | | This also make sure we remove the original coredump temporary file if we successfully managed to compress the coredump.
* coredump: replace Compression= setting by simpler Compress= boolean settingLennart Poettering2014-06-27
| | | | | | | Let's move things closer to journald's configuration settings, which knows Compress= already, as a boolean. This makes things more uniform, but also gives us more freedom to possibly swap out the used compression algorithm one day.
* coredump: don't expose the compression level as configuration optionLennart Poettering2014-06-27
| | | | | | | This sounds overly low-level and implementation-detaily. Let's just use the default level XZ suggests. This gives us more room to possibly swap out the compression algorithm used, as the compression level range will not leak into user configuration.
* journald: invoking fstatvfs() is now redundant in the vacuuming codeLennart Poettering2014-06-27
|
* coredump: don't be annoyed if another coredump hook removes our coredump ↵Lennart Poettering2014-06-27
| | | | while we work on it
* coredump: fix how the compression level is verifiedLennart Poettering2014-06-27
|
* coredump: add simple coredump vacuumingLennart Poettering2014-06-27
| | | | | | When disk space taken up by coredumps grows beyond a configured limit start removing the oldest coredump of the user with the most coredumps, until we get below the limit again.
* coredumpctl: fix potential deref of null pointerThomas Hindoe Paaboel Andersen2014-06-27
|
* coredump: make sure variable is set if uncompressedThomas Hindoe Paaboel Andersen2014-06-27
| | | | | reorder the code so the fstat is done before we can jump to uncompressed
* coredumpctl: remove unused variableThomas Hindoe Paaboel Andersen2014-06-26
|
* coredump: fix debug messageThomas Hindoe Paaboel Andersen2014-06-26
| | | | typo from 347272731e15d3c4a70fad7ccd7185e8e8059d01
* coredumpctl: fix HAVE_XZ checkDaniel Mack2014-06-26
|
* coredumpctl: fix build with !HAVE_XZDaniel Mack2014-06-26
| | | | | | | | | | | | | Fixes the following build error: CCLD coredumpctl src/journal/coredumpctl.o: In function `save_core': /src/systemd-master/src/journal/coredumpctl.c:656: undefined reference to `decompress_stream' collect2: error: ld returned 1 exit status make[2]: *** [coredumpctl] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2
* man: add coredump.conf(5)Zbigniew Jędrzejewski-Szmek2014-06-26
|
* coredump+coredumpctl: add COREDUMP_FILENAME, use in coredumpctlZbigniew Jędrzejewski-Szmek2014-06-26
|
* coredump: make compression configurableZbigniew Jędrzejewski-Szmek2014-06-26
| | | | | | | | | | | | Add Compression={none,xz} and CompressionLevel=0-9 settings. Defaults are xz/6. Compression=filesystem may be added later. I picked "xz" for the compression "type", since we might want to add different compressors later on. XZ is fairly memory and CPU intensive, and embedded users will likely want to use LZO or some other lightweight compression mechanism.
* coredump: compress core filesZbigniew Jędrzejewski-Szmek2014-06-26
| | | | | | | Unfortunately the core is first written uncompressed, then compressed by reading from disk and writing to the output file. This is ugly and slow, but I don't see a way around, if we want to get the backtrace without keeping everything in memory.
* journal/compress: add stream compression/decompression functionsZbigniew Jędrzejewski-Szmek2014-06-26
|
* journal/compress: simplify compress_blobZbigniew Jędrzejewski-Szmek2014-06-26
|
* tests: add test-compressRonny Chevalier2014-06-25
|
* coredump: log coredump even if core dumping failsZbigniew Jędrzejewski-Szmek2014-06-23
| | | | | Journal might be functional even if we cannot write to /var/lib/systemd/coredump.
* coredump: retrieve comm information from /procZbigniew Jędrzejewski-Szmek2014-06-23
| | | | | | | | | | | Kernel mangles comm information in an irreversible way when comm constains repeated spaces. Retrieve comm information from /proc, and only fallback to the information provided on the commandline when retrieving information from /proc fails. Add exe information to the list of saved xattr. https://bugs.freedesktop.org/show_bug.cgi?id=62043
* coredump: never write more than the configured processing size limit to diskLennart Poettering2014-06-23
|
* coredumpctl: show comm name next to PIDLennart Poettering2014-06-23
|
* coredump: quit early if we cannot store ay coredump to diskLennart Poettering2014-06-23
|
* coredumpctl: include timestamp information in "coredumpctl info" outputLennart Poettering2014-06-23
|
* coredump: also escape spaces in comm fields when formatting file namesLennart Poettering2014-06-23
|
* consistently order cleanup attribute before typeThomas Hindoe Paaboel Andersen2014-06-22
|
* coredump: fix include of xattr.hFilipe Brandenburger2014-06-20
| | | | | | | The correct path is now <sys/xattr.h> (from glibc-headers) and no longer <attr/xattr.h> (from libattr-devel.) Fixes: 34c10968cbe3b5591b3c0ce225b8694edd9709d0
* coredumpctl: add missing entries to --helpLennart Poettering2014-06-19
|
* coredumpctl: fix columns sizing for timestampLennart Poettering2014-06-19
|
* journal-send.c: use automatic cleanupZbigniew Jędrzejewski-Szmek2014-06-19
|
* journald: make SplitMode=uid the defaultLennart Poettering2014-06-19
| | | | | | | | | Now that we actually can distuingish system and normal users there's no point in taking session information into account anymore when splitting up logs. This has the beenfit with that coredump information will actually end up in each user's own journal.
* coredumpctl: introduce new -1 switch for showing a single, most recent entry ↵Lennart Poettering2014-06-19
| | | | | | | only "coredumpctl info -1" is now incredibly useful for showing the most recent stacktrace.
* coredump: simplify how we apply extended attributes to coredumpsLennart Poettering2014-06-19
|
* coredump: include stacktrace of coredumps in the log messageLennart Poettering2014-06-19
| | | | | elfutils' libdw is maintained, can read DWARF debug data and appears to be the library of choice for generating backtraces today.
* coredump: add 3 more metadata fields to coredump entriesLennart Poettering2014-06-19
|
* coredump: add new "info" verb to coredumpctl showing detailed information ↵Lennart Poettering2014-06-19
| | | | about a coredump
* coredump: make sure coredumpctl can handle externally stored coredumpsLennart Poettering2014-06-19
|
* coredump: optionally store coredumps on disk, not in the journalLennart Poettering2014-06-19
| | | | | | | | Introduce a new configuration file /etc/systemd/coredump.conf to configure when to place coredumps in the journal and when on disk. Since the coredumps are quite large, default to storing them only on disk.
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-02 00:03:54 +0000