5dd55303f4
$ coredumpctl info |grep Command Command Line: bash -c kill -SEGV $$ (before) Command Line: bash -c "kill -SEGV \$\$" (road not taken, C quotes) Command Line: bash -c $'kill -SEGV $$' (now, POSIX quotes) Before we wouldn't use any quoting, making it impossible to figure how the command line was split into arguments. We could use "normal" quotes, but this has the disadvantage that the commandline *looks* like it could be pasted into the terminal and executed, but this is not true: various non-printable characters cannot be expressed in this quoting style. (This is not visible in this example). Thus, "POSIX quotes" are used, which should allow any command line to be expressed acurrately and pasted directly into a shell prompt to reexecute. I wonder if we should another field in the coredump entry that simply shows the original cmdline with embedded NULs, in the original /proc/*/cmdline format. This would allow clients to format the data as they see fit. But I think we'd want to keep the serialized form anyway, for backwards compatibility.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.