On Tue, 01.03.11 23:36, Andrey Borzenkov ([email protected]) wrote: > > On Tue, Mar 1, 2011 at 10:51 PM, Lennart Poettering > <[email protected]> wrote: > >> > The only problem with that > >> > I see is that syslog implementations started with sysv scripts would end > >> > up in a cyclic loop, and I don't know how to fix this... > >> > > >> > >> Could you elaborate? Do you mean messages may be echoed back to > >> stdout/stderr to create a loop? > > > > Well, the problem goes like this: syslog.service is a SysV service. It > > is pulled in by syslog.target. Now you enable your new feature, i.e. all > > output to stdout and stderr of all SysV services will go to syslog, and > > all sysv services will gain a dep on syslog.target. Boom, you have your > > cyclic dependency: syslog.service and syslog.target will require each > > other. > > > > But setting output to syslog does not pull in syslog.target; it pulls > in systemd-logger.socket. It should not really cause any loops as far > as I can tell. Or do I miss something?
Well, that's actually true, but this doesn't really fix the problem: you still have a weird feedback loop. everything syslog writes to stdout/stderr would be fed back to syslog, which is nothing we want. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
