On Monday 09 June 2014 at 23:32:28, Mike Gilbert wrote: > On Mon, Jun 9, 2014 at 4:42 PM, Reindl Harald <h.rei...@thelounge.net> wrote: > > > > Am 09.06.2014 22:32, schrieb Leonid Isaev: > >> On Mon, Jun 09, 2014 at 09:19:20PM +0200, Reindl Harald wrote: > >>> [...] > >>> > >>> on our production infrastrcuture these messages would be > >>> *a lot* more than all other logs summarized > >>> > >>> *and* they are spitted to /var/log/messages to make things worst > >>> > >>>> But why can't you write a syslog filter which uses facility as well as > >>>> program > >>>> name? So if you believe that systemd-generated messages are useless, > >>>> drop them > >>> > >>> because you *can not* distinguish between *that* user messages > >>> and system message sbecause they have systemd as program name > >>> common, the PID changes and you don't want to drop *system > >>> messages* from systemd > >> > >> So, systemd starts certain things on _any_ user "login": be it a real > >> user, or > >> a daemon. However > > > > * why do it need to do that much stuff > > * why can't it keep that stuff long-running > > > > you have already "/usr/lib/systemd/systemd --user" and "(sd-pam)" > > processes for every userid ever started a cronjob running all > > the time - so why flood the logs every minute again? > > > > Now that you mention it, you can cut down on a lot of the log spam by > enabling "linger" for root and other users which run cron jobs. > > loginctl enable-linger <user> > > This will keep a systemd user instance running so that a new one is > not spawned every time cron wakes up.
It's more interesting, why a logind session is ever being created for the cron job... It shouldn't be that way, or do I misunderstand something? -- Ivan Shapovalov / intelfx /
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
