On Wed, Feb 23, 2011 at 10:48 AM, Mike Kazantsev <mk.frag...@gmail.com> wrote: > Good day, > > > I've recently deployed systemd on a machine that uses some syslog > monitoring software and the software went nuts because messages from > systemd logger were inconsistent with other logging - they all look > like this: > > kernel.warning kernel[-]: process[pid]: message contents >
I confirm this at least for one special case - redirecting service output to syslog. Here is how it looks like: Mar 1 06:35:53 localhost kernel: crond[847]: Starting crond: [ OK ]^M[ OK ] Mar 1 06:35:53 localhost kernel: atd[850]: Starting atd: [ OK ] Syslog output from other programs is OK, so it looks like internal systemd issue. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
