Description of problem:
systemd-journal-remote is basically unusable:
 - when receiving logs it fills the filesystem (512 MiB) too quickly, weird rotation of journal happens, filesystem limits (default or configured) are not honored and service+socket shortly fail
   - issue is reported upstream https://github.com/systemd/systemd/issues/1387
 - using --compress doesn't help much
 - example:
$ sudo systemctl start systemd-journal-remote.socket
$ sudo journalctl -D /var/log/journal/remote/ | wc -l
68523
$ du -h /var/log/journal/remote/
102M    /var/log/journal/remote/
...
$ sudo journalctl -D /var/log/journal/remote/ | wc -l
68547
$ du -h /var/log/journal/remote/
115M    /var/log/journal/remote/
... etc.


Version-Release number of selected component (if applicable):
systemd-journal-gateway-219-19.el7_2.7.x86_64

How reproducible:
Always

Steps to Reproduce:
Configure systemd-journal-upload to send logs to systemd-journal-remote, including necessary fixes as mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1327303 and notice filesystem fill up too quickly compared to minimal amount of messages.

Actual results:
Filesystem is filled up quickly, bad rotation of journal happens and service+socket shortly fail.

Expected results:
systemd-journal-remote should receive messages from systemd-journal-upload, honor default or configured limits, and rotate remote journal files.

Additional info:
https://github.com/systemd/systemd/issues/1387