I at least verified the update doesn't appear to cause any obvious regression:
start server:
ubuntu@lp1698388-x:~$ dpkg -l |grep systemd-journal-remote ii systemd-journal-remote 229-4ubuntu21.29 amd64 tools for sending and receiving remote journal logs ubuntu@lp1698388-x:~$ mkdir /tmp/journal-test ubuntu@lp1698388-x:~$ /lib/systemd/systemd-journal-remote -o /tmp/journal-test --listen-http=127.0.0.1:7000
then in separate terminal:
ubuntu@lp1698388-x:~$ /lib/systemd/systemd-journal-upload -u http://127.0.0.1:7000
then check if uploaded:
ubuntu@lp1698388-x:~$ ls -l /tmp/journal-test/ total 8196 -rw-r----- 1 ubuntu ubuntu 8388608 Sep 10 17:03 remote-127.0.0.1.journal ubuntu@lp1698388-x:~$ journalctl --file /tmp/journal-test/remote-127.0.0.1.journal | wc -l 1842
I at least verified the update doesn't appear to cause any obvious regression:
start server:
ubuntu@ lp1698388- x:~$ dpkg -l |grep systemd- journal- remote journal- remote 229-4ubuntu21.29 amd64 tools for sending and receiving remote journal logs lp1698388- x:~$ mkdir /tmp/journal-test lp1698388- x:~$ /lib/systemd/ systemd- journal- remote -o /tmp/journal-test --listen- http=127. 0.0.1:7000
ii systemd-
ubuntu@
ubuntu@
then in separate terminal:
ubuntu@ lp1698388- x:~$ /lib/systemd/ systemd- journal- upload -u http:// 127.0.0. 1:7000
then check if uploaded:
ubuntu@ lp1698388- x:~$ ls -l /tmp/journal-test/ 127.0.0. 1.journal lp1698388- x:~$ journalctl --file /tmp/journal- test/remote- 127.0.0. 1.journal | wc -l
total 8196
-rw-r----- 1 ubuntu ubuntu 8388608 Sep 10 17:03 remote-
ubuntu@
1842