summaryrefslogtreecommitdiffstats
path: root/man/journal-remote.conf.xml (unfollow)
Commit message (Collapse)AuthorFilesLines
2019-02-27network: fix error code in logYu Watanabe1-1/+1
2019-02-27network: merge conditions and use FLAGS_SET() macroYu Watanabe1-6/+6
2019-02-27network: make ndisc_router_process_options() propagate errorYu Watanabe1-15/+11
And its caller ignore the error.
2019-02-27fs-util: add missing linux/falloc.h includeDavide Cavalca1-0/+1
2019-02-26fuzz-ndisc-rs: avoid assertion failure on samples which dont fit in pipeZbigniew Jędrzejewski-Szmek2-0/+5
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11605.
2019-02-26fuzz-lldp: avoid assertion failure on samples which dont fit in pipeZbigniew Jędrzejewski-Szmek2-0/+5
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11603.
2019-02-26fuzz-journal-stream: avoid assertion failure on samples which don't fit in pipeZbigniew Jędrzejewski-Szmek2-1/+3
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11587. We had a sample which was large enough that write(2) failed to push all the data into the pipe, and an assert failed. The code could be changed to use a loop, but then we'd need to interleave writes and sd_event_run (to process the journal). I don't think the complexity is worth it — fuzzing works best if the sample is not too huge anyway. So let's just reject samples above 64k, and tell oss-fuzz about this limit.
2019-02-26sd-bus: add methods and signals parameter names. Fixes: #1564Giacinto Cifelli6-15/+226
2019-02-26shared/ask-password-api: when echoing multi-byte characters, print the whole ↵Zbigniew Jędrzejewski-Szmek1-1/+4
sequence This is untested, but I don't see how the previous code could have worked for multibyte characters (with echo on).
2019-02-26basic/utf8: do not read past end of string when looking for a multi-byte ↵Zbigniew Jędrzejewski-Szmek8-26/+42
character Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9341.
2019-02-26basic/utf8: change type of function to emphasize that it only looks at one ↵Zbigniew Jędrzejewski-Szmek1-9/+4
character
2019-02-26core: consider non-SERVICE_EXEC_START commands for EXIT_CLEAN_COMMANDAnita Zhang1-1/+9
When there are multiple ExecStop= statements, the next command would continue to run even after TimeoutStopSec= is up and sends SIGTERM. This is because, unless Type= is oneshot, the exit code/status would evaluate to SERVICE_SUCCESS in service_sigchld_event()'s call to is_clean_exit(). This success indicates following commands would continue running until the end of the list is reached, or another timeout is hit and SIGKILL is sent. Since long running processes should not be invoked in non-SERVICE_EXEC_START commands, consider them for EXIT_CLEAN_COMMAND instead of EXIT_CLEAN_DAEMON. Passing EXIT_CLEAN_COMMAND to is_clean_exit() evaluates the SIGTERM exit code/status to failure and will stop execution after the first timeout is hit. Fixes #11431