On Sun, Apr 10, 2016 at 1:57 PM, Samuel Williams < space.ship.travel...@gmail.com> wrote:
> Hello, > > > I've been trying to figure out the best way to support legacy applications > that don't support syslog for logging. The best we can do, I think, is to > use fifo and have another process read the fifo to journald. > > > I made the following unit journald-fifo@.service > > > [Unit] > > Description=A fifo for logging to journald > > AssertPathExists=/var/log/%i.fifo > > > [Service] > > Type=simple > > ExecStart=/bin/sh -c 'while true; do systemd-cat -t %i < /var/log/%i.fifo; > done' > > Nice=5 > > > [Install] > > WantedBy=multi-user.target > > I was wondering is this a good approach? Is there a better way? (of > course, we'd like to fix the original software to work better). > If the software can log to stdout/stderr, just use that. If not, make it write logs to "/dev/stderr". Either way, systemd will log service stdout automatically. -- Mantas Mikulėnas <graw...@gmail.com>
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
