On Fri, 17.01.14 16:52, David Timothy Strauss (da...@davidstrauss.net) wrote:
> It would be nice if bootup could realize the journal queue is full and > wait for journal startup before proceeding further. It might cause > some annoying non-determinism, though. Not following here. Logging in syslog and the journal is synhchronous: as soon as the socket fills up the clients start to block until the other side made space again. THis means that no messages should be lost and boot-up should be neatly synchronized to the logging sserver speed. Note that by default the socket buffer is really small. The kernel puts a limit to 15 messages by default, (/proc/sys/net/unix/max_dgram_qlen can be used to change this, unfortunately only globally), and the socket buffer limit in bytes is pretty short too... -- the latter is now bumped if possible with systemd git, but that only works with priviliged clients... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
