[systemd-devel] rsync output is not captured in the journal

Mantas Mikulėnas grawity at gmail.com
Mon Jan 5 04:04:32 PST 2015


On Mon, Jan 5, 2015 at 1:44 PM, Igor Bukanov <igor at mir2.org> wrote:
> On 5 January 2015 at 12:21, Mantas Mikulėnas <grawity at gmail.com> wrote:
>> Run it under `strace -D` – the problem may be related to rsync's
>> parent being pid1.
>
> Under strace -D the problem disappeared as well. The problem also
> disappears if I run rsync like in:
>
> ExecStart=/usr/bin/bash -c 'exec /usr/bin/rsync -vv /etc/hostname /tmp/h3'
>
> So the only way to see the problem is using rsync directly in
> ExecStart like in    ExecStart=/usr/bin/rsync -vv /etc/hostname /tmp/

Attach `strace -f -p 1` to systemd then, and have it follow forks.

Perhaps also trace journald (the receiving end of rsync's stdout).

-- 
Mantas Mikulėnas <grawity at gmail.com>


More information about the systemd-devel mailing list