On Mon, 09.06.14 12:01, Mantas Mikulėnas (graw...@gmail.com) wrote:
I think there's also another problem – logind starts the user manager
instance for cronjobs while it shouldn't do so for batch stuff. Probably a
PAM configuration issue.
Nope. This is intentional. A session is a session is a
On 10.06.2014 13:20, Lennart Poettering wrote:
On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
After upgrading systemd 208 - 212, every single cron job creates
this flood in systemd journal:
Can I quiet this down somehow?
The idea with the journal is that we log everything that
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
Am 10.06.2014 12:20, schrieb Lennart Poettering:
On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
After upgrading systemd 208 - 212, every single cron job creates
this flood in systemd journal:
Can I quiet this down somehow?
The idea with the journal is that we log
On Tue, 10.06.14 13:24, Leho Kraav (l...@kraav.com) wrote:
On 10.06.2014 13:20, Lennart Poettering wrote:
On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
After upgrading systemd 208 - 212, every single cron job creates
this flood in systemd journal:
Can I quiet this down
On 10.06.2014 19:01, Lennart Poettering wrote:
In the meantime mgilbert's suggestion for using EDIT **loginctl enable-linger**
command seems to accomplish the goal of quieting cron logging. Any
side effects to consider?
Well, you keep the systemd user instance running all the time then
On Tue, 10.06.14 14:31, Ivan Shapovalov (intelfx...@gmail.com) wrote:
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?
We should create a logind session for all sessions of normal users. It
On 09.06.2014 09:33, Leho Kraav wrote:
After upgrading systemd 208 - 212, every single cron job creates this
flood in systemd journal:
juuni 09 09:20:01 xps14 crond[15112]: pam_unix(crond:session): session
opened for user root by (uid=0)
juuni 09 09:20:01 xps14 systemd[15113]:
Am 10.06.2014 18:01, schrieb Lennart Poettering:
On Tue, 10.06.14 13:24, Leho Kraav (l...@kraav.com) wrote:
On 10.06.2014 13:20, Lennart Poettering wrote:
On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
After upgrading systemd 208 - 212, every single cron job creates
this flood
On Tue, 10.06.14 19:03, Leho Kraav (l...@kraav.com) wrote:
On 10.06.2014 19:01, Lennart Poettering wrote:
In the meantime mgilbert's suggestion for using EDIT **loginctl
enable-linger**
command seems to accomplish the goal of quieting cron logging. Any
side effects to consider?
Well,
On Tue, 10.06.14 20:05, Leho Kraav (l...@kraav.com) wrote:
On 09.06.2014 09:33, Leho Kraav wrote:
After upgrading systemd 208 - 212, every single cron job creates this
flood in systemd journal:
juuni 09 09:20:01 xps14 crond[15112]: pam_unix(crond:session): session
opened for user root by
After upgrading systemd 208 - 212, every single cron job creates this
flood in systemd journal:
juuni 09 09:20:01 xps14 crond[15112]: pam_unix(crond:session): session
opened for user root by (uid=0)
juuni 09 09:20:01 xps14 systemd[15113]: pam_unix(systemd-user:session):
session opened for
I think there's also another problem – logind starts the user manager
instance for cronjobs while it shouldn't do so for batch stuff. Probably a
PAM configuration issue.
--
Mantas Mikulėnas graw...@gmail.com
On Jun 9, 2014 9:34 AM, Leho Kraav l...@kraav.com wrote:
After upgrading systemd 208 -
On Mon, Jun 09, 2014 at 10:48:31AM +0300, Leho Kraav wrote:
Date: Mon, 09 Jun 2014 10:48:31 +0300
From: Leho Kraav l...@kraav.com
To: Reindl Harald h.rei...@thelounge.net,
systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] How to quiet cron sessions logging with
systemd-212
to quiet cron sessions logging with
systemd-212?
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101
Thunderbird/24.5.0
On 09.06.2014 10:43, Reindl Harald wrote:
nobody cares because the developers point of view is that what is
interesting for them needs to be also faced
On Mon, Jun 09, 2014 at 08:08:43PM +0200, Reindl Harald wrote:
Date: Mon, 09 Jun 2014 20:08:43 +0200
From: Reindl Harald h.rei...@thelounge.net
To: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] How to quiet cron sessions logging with
systemd-212?
User-Agent: Mozilla/5.0
Am 09.06.2014 21:07, schrieb Leonid Isaev:
On Mon, Jun 09, 2014 at 08:08:43PM +0200, Reindl Harald wrote:
all the decades before crond did run fine, logs exactly what
you need to know if /var/log/secure and /var/log/crond
without writing *hundret thousands* loglines all day long
on machines
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
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
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
20 matches
Mail list logo
