-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, This is what appears in the /var/log/messages log when a trivial crom job runs: <3.6> 2021-08-15 02:00:01 minas-tirith systemd 1 - - Created slice User Slice of UID 9. <3.6> 2021-08-15 02:00:01 minas-tirith systemd 1 - - Starting User Runtime Directory /run/user/9... <3.6> 2021-08-15 02:00:01 minas-tirith systemd 1 - - Started Timeline of Snapper Snapshots. <3.6> 2021-08-15 02:00:01 minas-tirith systemd 1 - - Started User Runtime Directory /run/user/9. <3.6> 2021-08-15 02:00:01 minas-tirith dbus-daemon 1447 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.291' (uid=0 pid=27711 comm="/usr/lib/snapper/systemd-helper --timeline ") (using servicehelper) <3.6> 2021-08-15 02:00:01 minas-tirith systemd 1 - - Starting User Manager for UID 9... <10.6> 2021-08-15 02:00:01 minas-tirith systemd - - - pam_unix(systemd-user:session): session opened for user news by (uid=0) <3.6> 2021-08-15 02:00:02 minas-tirith dbus-daemon 1447 - - [system] Successfully activated service 'org.opensuse.Snapper' <3.6> 2021-08-15 02:00:02 minas-tirith systemd 27713 - - Starting D-Bus User Message Bus Socket. <3.6> 2021-08-15 02:00:02 minas-tirith systemd 27713 - - Listening on Sound System. <3.6> 2021-08-15 02:00:02 minas-tirith systemd 27713 - - Listening on Multimedia System. <3.6> 2021-08-15 02:00:02 minas-tirith systemd 27713 - - Listening on D-Bus User Message Bus Socket. <3.6> 2021-08-15 02:00:02 minas-tirith systemd 1 - - Started User Manager for UID 9. <3.6> 2021-08-15 02:00:02 minas-tirith systemd 1 - - Started Session 18 of user news. <10.6> 2021-08-15 02:00:02 minas-tirith cron 27675 - - pam_unix(crond:session): session opened for user news by (uid=0) <10.6> 2021-08-15 02:00:04 minas-tirith CRON 27675 - - pam_unix(crond:session): session closed for user news <3.6> 2021-08-15 02:00:14 minas-tirith systemd 1 - - user-runtime-dir@9.service: Unit not needed anymore. Stopping. <3.6> 2021-08-15 02:00:14 minas-tirith systemd 1 - - Stopping User Manager for UID 9... <3.6> 2021-08-15 02:00:14 minas-tirith systemd 27713 - - Closed Sound System. <3.6> 2021-08-15 02:00:14 minas-tirith systemd 27713 - - Closed Multimedia System. <3.6> 2021-08-15 02:00:14 minas-tirith systemd 27713 - - Closed D-Bus User Message Bus Socket. <3.6> 2021-08-15 02:00:14 minas-tirith systemd 27713 - - Reached target Shutdown. <3.6> 2021-08-15 02:00:14 minas-tirith systemd 27713 - - Starting Exit the Session... <3.6> 2021-08-15 02:00:14 minas-tirith systemd 27713 - - Received SIGRTMIN+24 from PID 27726 (kill). <10.6> 2021-08-15 02:00:14 minas-tirith systemd - - - pam_unix(systemd-user:session): session closed for user news <3.6> 2021-08-15 02:00:14 minas-tirith systemd 1 - - user-runtime-dir@9.service: Unit not needed anymore. Stopping. <3.6> 2021-08-15 02:00:14 minas-tirith systemd 1 - - Stopped User Manager for UID 9. <3.6> 2021-08-15 02:00:14 minas-tirith systemd 1 - - user-runtime-dir@9.service: Unit not needed anymore. Stopping. <3.6> 2021-08-15 02:00:14 minas-tirith systemd 1 - - user-9.slice: Unit not needed anymore. Stopping. <3.6> 2021-08-15 02:00:14 minas-tirith systemd 1 - - Stopping User Runtime Directory /run/user/9... <3.6> 2021-08-15 02:00:14 minas-tirith systemd 1 - - Stopped User Runtime Directory /run/user/9. <3.6> 2021-08-15 02:00:14 minas-tirith systemd 1 - - user-9.slice: Unit not needed anymore. Stopping. <3.6> 2021-08-15 02:00:14 minas-tirith systemd 1 - - Removed slice User Slice of UID 9. The cronjob line (in /etc/crontab): - -*/5 * * * * news /usr/local/bin/getnews.cronjob In the past, the "-" kept the log silent, but since the advent of systemd that went out of the window. Is there some way to reduce that to nothing, or at least one or two lines? - -- Cheers, Carlos E. R. (from openSUSE Leap 15.2 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCYRhkORwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcsuMA/0/F7Og7fRxps0iljGpg /f2h1Pw8SMIzmF2EHbzBUTEkAP9zBPWOJ2UKr855CudHtBrBPJbdLFMEjoJTNJ+5 xUX4JA== =qHZ8 -----END PGP SIGNATURE-----
Carlos E. R. wrote:
Is there some way to reduce that to nothing, or at least one or two lines?
I was going to say - look at your systemd loglevel, but I don't see all that output on a couple of Leap and TW systems I have just looked at. -- Per Jessen, Zürich (26.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2021-08-15 a las 11:24 +0200, Per Jessen escribió:
Carlos E. R. wrote:
Is there some way to reduce that to nothing, or at least one or two lines?
I was going to say - look at your systemd loglevel, but I don't see all that output on a couple of Leap and TW systems I have just looked at.
I have no systemd journal, I have it disabled: Aug 13 21:35:51 minas-tirith kernel: random: systemd: uninitialized urandom read (16 bytes read) Aug 13 21:35:51 minas-tirith kernel: random: systemd: uninitialized urandom read (16 bytes read) Aug 13 21:35:51 minas-tirith kernel: random: systemd: uninitialized urandom read (16 bytes read) Aug 13 21:35:51 minas-tirith kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Aug 13 21:35:51 minas-tirith kernel: scsi 1:0:0:0: Attached scsi generic sg1 type 5 Aug 13 21:35:51 minas-tirith systemd-journald[167]: Journal started Aug 13 21:35:51 minas-tirith systemd-journald[167]: Runtime journal (/run/log/journal/7b3efb92d4779debd063b9394aef7162) is 3.7M, max> Aug 13 21:35:51 minas-tirith kernel: [Firmware Bug]: Invalid critical threshold (0) Aug 13 21:35:53 minas-tirith systemd[1]: Switching root. Aug 13 21:35:53 minas-tirith systemd-journald[167]: Journal stopped I'll activate it again, but it will fill up with thousand of entries from leafnode. There is no filtering possible. ... Hum. After fifteen minutes, the journal has nothing about the cronjob. Syslog has a lot. Same time interval. - -- Cheers Carlos E. R. (from openSUSE Leap 15.2 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCYRj2ARwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcEucA/R2nllBV/xuTE+/ojjAg yL4/Av0qcer/FaFo418CqDjvAP9JTGyaa4wH3NFZmDDzeodUPPRljwQrGOgpbUVs uhShWg== =zvN4 -----END PGP SIGNATURE-----
On 15.08.2021 12:24, Per Jessen wrote:
Carlos E. R. wrote:
Is there some way to reduce that to nothing, or at least one or two lines?
I was going to say - look at your systemd loglevel, but I don't see all that output on a couple of Leap and TW systems I have just looked at.
And you run jobs from within root crontab as different user? I most certainly do see it when running as non-root. The only way to avoid it is to remove pam_systemd from crond pam config.
On 15/08/2021 13.11, Andrei Borzenkov wrote:
On 15.08.2021 12:24, Per Jessen wrote:
Carlos E. R. wrote:
Is there some way to reduce that to nothing, or at least one or two lines?
I was going to say - look at your systemd loglevel, but I don't see all that output on a couple of Leap and TW systems I have just looked at.
And you run jobs from within root crontab as different user? I most certainly do see it when running as non-root.
Yep: -*/5 * * * * news /usr/local/bin/getnews.cronjob ****
The only way to avoid it is to remove pam_systemd from crond pam config.
Huh. :-? Would a systemd timer be that verbose? -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 15.08.2021 14:29, Carlos E. R. wrote:
On 15/08/2021 13.11, Andrei Borzenkov wrote:
On 15.08.2021 12:24, Per Jessen wrote:
Carlos E. R. wrote:
Is there some way to reduce that to nothing, or at least one or two lines?
I was going to say - look at your systemd loglevel, but I don't see all that output on a couple of Leap and TW systems I have just looked at.
And you run jobs from within root crontab as different user? I most certainly do see it when running as non-root.
Yep:
-*/5 * * * * news /usr/local/bin/getnews.cronjob ****
I know. I replied to Per.
The only way to avoid it is to remove pam_systemd from crond pam config.
Huh. :-?
Would a systemd timer be that verbose?
And what exactly prevents you from testing it? No, it won't be *that* verbose.
On 15/08/2021 13.52, Andrei Borzenkov wrote:
On 15.08.2021 14:29, Carlos E. R. wrote:
On 15/08/2021 13.11, Andrei Borzenkov wrote:
...
Would a systemd timer be that verbose?
And what exactly prevents you from testing it?
because I have no idea how to do it...
No, it won't be *that* verbose.
Ok, I'll try to learn that thing. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Carlos E. R. wrote:
On 15/08/2021 13.52, Andrei Borzenkov wrote:
On 15.08.2021 14:29, Carlos E. R. wrote:
On 15/08/2021 13.11, Andrei Borzenkov wrote:
...
Would a systemd timer be that verbose?
And what exactly prevents you from testing it?
because I have no idea how to do it...
Google will help with that - besides, there are other timer units, you can start by copying one. -- Per Jessen, Zürich (28.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
On 15/08/2021 14.25, Per Jessen wrote:
Carlos E. R. wrote:
On 15/08/2021 13.52, Andrei Borzenkov wrote:
On 15.08.2021 14:29, Carlos E. R. wrote:
On 15/08/2021 13.11, Andrei Borzenkov wrote:
...
Would a systemd timer be that verbose?
And what exactly prevents you from testing it?
because I have no idea how to do it...
Google will help with that - besides, there are other timer units, you can start by copying one.
Yes, yes. But doing all that work before knowing if it will be less verbose is not interesting, which is why I asked, someone might know. Once I know there is hope, I can invest the effort ;-) -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 15/08/2021 14.48, Carlos E. R. wrote:
On 15/08/2021 14.25, Per Jessen wrote:
Carlos E. R. wrote:
On 15/08/2021 13.52, Andrei Borzenkov wrote:
On 15.08.2021 14:29, Carlos E. R. wrote:
On 15/08/2021 13.11, Andrei Borzenkov wrote:
...
Would a systemd timer be that verbose?
And what exactly prevents you from testing it?
because I have no idea how to do it...
Google will help with that - besides, there are other timer units, you can start by copying one.
Yes, yes. But doing all that work before knowing if it will be less verbose is not interesting, which is why I asked, someone might know. Once I know there is hope, I can invest the effort ;-)
All timers in /var/lib/systemd/timers are zero bytes. ... Whoa! It already exists: /usr/lib/systemd/system/leafnode-hourly.timer [Unit] Description=fetching news messages spool hourly [Timer] OnBootSec=15min OnUnitActiveSec=1h [Install] WantedBy=timers.target /usr/lib/systemd/system/leafnode-hourly.service: [Unit] Description=fetching news messages spool hourly After=network.target [Service] User=news ExecStart=/usr/sbin/fetchnews [Install] WantedBy=multi-user.target -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2021-08-15 a las 14:57 +0200, Carlos E. R. escribió:
On 15/08/2021 14.48, Carlos E. R. wrote:
...
Whoa! It already exists:
/usr/lib/systemd/system/leafnode-hourly.timer
[Unit] Description=fetching news messages spool hourly
[Timer] OnBootSec=15min OnUnitActiveSec=1h
[Install] WantedBy=timers.target
/usr/lib/systemd/system/leafnode-hourly.service: [Unit] Description=fetching news messages spool hourly After=network.target
[Service] User=news ExecStart=/usr/sbin/fetchnews
[Install] WantedBy=multi-user.target
I edited both files to suit my needs: minas-tirith:~ # systemctl edit leafnode-hourly.timer [Unit] Description=fetching news messages spool hourly [Timer] OnBootSec=15min OnUnitActiveSec=5min [Install] WantedBy=timers.target minas-tirith:~ # systemctl edit leafnode-hourly.service [Unit] Description=fetching news messages spool hourly After=network.target [Service] User=news ExecStart=/usr/local/bin/getnews.cronjob [Install] WantedBy=multi-user.target minas-tirith:~ # systemctl --now enable leafnode-hourly.timer Job for leafnode-hourly.timer failed. See "systemctl status leafnode-hourly.timer" and "journalctl -xe" for details. minas-tirith:~ # journalctl -xe minas-tirith:~ # systemctl status leafnode-hourly.timer ● leafnode-hourly.timer - fetching news messages spool hourly Loaded: loaded (/usr/lib/systemd/system/leafnode-hourly.timer; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/leafnode-hourly.timer.d └─override.conf Active: inactive (dead) Trigger: n/a Aug 15 18:18:36 minas-tirith.valinor systemd[1]: leafnode-hourly.timer: Refusing to start, unit to trigger not loaded. Aug 15 18:18:36 minas-tirith.valinor systemd[1]: Failed to start fetching news messages spool hourly. Aug 15 18:25:47 minas-tirith.valinor systemd[1]: leafnode-hourly.timer: Refusing to start, unit to trigger not loaded. Aug 15 18:25:47 minas-tirith.valinor systemd[1]: Failed to start fetching news messages spool hourly. minas-tirith:~ # Aug 15 18:25:47 minas-tirith.valinor systemd-sysv-generator[10533]: stat() failed on /etc/init.d/jexec, ignoring: No such file or directory Aug 15 18:25:47 minas-tirith.valinor systemd[1]: leafnode-hourly.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing. Aug 15 18:25:47 minas-tirith.valinor systemd[1]: leafnode-hourly.timer: Refusing to start, unit to trigger not loaded. Aug 15 18:25:47 minas-tirith.valinor systemd[1]: Failed to start fetching news messages spool hourly. - -- Subject: Unit leafnode-hourly.timer has failed - -- Defined-By: systemd - -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel - -- - -- Unit leafnode-hourly.timer has failed. - -- - -- The result is failed. Two "ExecStart="? I only see one when I *edit* the file! {baffled} - -- Cheers Carlos E. R. (from openSUSE Leap 15.2 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCYRlCchwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcBAYA/iuET8bVUVVmgONwPywt SBLi4VtO2Oij4NgvXgmlULPLAQCQ4MRNrDRq0FcqiVL6qx2RaqfeHui46WglZ/9Z zL/pjA== =FVk+ -----END PGP SIGNATURE-----
On Sun, 15 Aug 2021 18:36, Carlos E. R. <robin.listas@...> wrote:
El 2021-08-15 a las 14:57 +0200, Carlos E. R. escribió:
On 15/08/2021 14.48, Carlos E. R. wrote:
[snip]
minas-tirith:~ # systemctl edit leafnode-hourly.service
[Unit] Description=fetching news messages spool hourly After=network.target
[Service] User=news ExecStart=/usr/local/bin/getnews.cronjob
[Install] WantedBy=multi-user.target
in this you have the error, and it is insidious
Two "ExecStart="? I only see one when I *edit* the file! {baffled}
Yep! Thanks to the "gods" who have given us the syntax of the service-files you have to do it differently. First you have to accecpt that multiple ExecStart= lines are possible. Second you have to learn that you can "clear" the existing ExecStart= line, and do it BEFORE you define your own. Third is to combine all that: 1. Clear 2. Define your own. Example here for your Service section: [Service] User=news ExecStart= ExecStart=/usr/local/bin/getnews.cronjob Closing comment: Yep. I've also struggled with that. Lost some days on it. Not happy at all with it. -Yamaban
On 15/08/2021 18.54, Yamaban wrote:
On Sun, 15 Aug 2021 18:36, Carlos E. R. <robin.listas@...> wrote:
El 2021-08-15 a las 14:57 +0200, Carlos E. R. escribió:
On 15/08/2021 14.48, Carlos E. R. wrote:
[snip]
minas-tirith:~ # systemctl edit leafnode-hourly.service
[Unit] Description=fetching news messages spool hourly After=network.target
[Service] User=news ExecStart=/usr/local/bin/getnews.cronjob
[Install] WantedBy=multi-user.target
in this you have the error, and it is insidious
Two "ExecStart="? I only see one when I *edit* the file! {baffled}
And, edit is not edit, but override. I thought I was doing a real edit, a replace of the file. [...] As Andrei says, I was not using "---full".
Yep! Thanks to the "gods" who have given us the syntax of the service-files you have to do it differently.
First you have to accecpt that multiple ExecStart= lines are possible.
Second you have to learn that you can "clear" the existing ExecStart= line, and do it BEFORE you define your own.
Third is to combine all that: 1. Clear 2. Define your own.
Example here for your Service section:
[Service] User=news ExecStart= ExecStart=/usr/local/bin/getnews.cronjob
Gosh! yes, now it works.
Closing comment: Yep. I've also struggled with that. Lost some days on it. Not happy at all with it.
Thanks! :-) Final files: minas-tirith:~ # systemctl cat leafnode-hourly.service # /usr/lib/systemd/system/leafnode-hourly.service [Unit] Description=fetching news messages spool hourly After=network.target [Service] User=news ExecStart=/usr/sbin/fetchnews [Install] WantedBy=multi-user.target # /etc/systemd/system/leafnode-hourly.service.d/override.conf [Service] ExecStart= ExecStart=/usr/local/bin/getnews.cronjob minas-tirith:~ # minas-tirith:~ # systemctl cat leafnode-hourly.timer # /usr/lib/systemd/system/leafnode-hourly.timer [Unit] Description=fetching news messages spool hourly [Timer] OnBootSec=15min OnUnitActiveSec=1h [Install] WantedBy=timers.target # /etc/systemd/system/leafnode-hourly.timer.d/override.conf [Timer] OnUnitActiveSec=5min minas-tirith:~ # -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 15.08.2021 19:36, Carlos E. R. wrote:
Two "ExecStart="? I only see one when I *edit* the file! {baffled}
ExecStart directive can have multiple values (the second entry does not replace the first one), you need to assign empty value to clear it before your own value. Or use "systemctl edit --full".
On 15/08/2021 13.55, Carlos E. R. wrote:
On 15/08/2021 13.52, Andrei Borzenkov wrote:
On 15.08.2021 14:29, Carlos E. R. wrote:
On 15/08/2021 13.11, Andrei Borzenkov wrote: ...
Would a systemd timer be that verbose?
And what exactly prevents you from testing it? because I have no idea how to do it...
No, it won't be *that* verbose. Ok, I'll try to learn that thing.
It is less verbose: nothing is logged to syslog, as far as I can see. -- Saludos/Cheers Carlos E. R.
On 15/08/2021 19.08, Carlos E.R. wrote:
On 15/08/2021 13.55, Carlos E. R. wrote:
On 15/08/2021 13.52, Andrei Borzenkov wrote:
On 15.08.2021 14:29, Carlos E. R. wrote:
On 15/08/2021 13.11, Andrei Borzenkov wrote: ...
Would a systemd timer be that verbose?
And what exactly prevents you from testing it? because I have no idea how to do it...
No, it won't be *that* verbose. Ok, I'll try to learn that thing.
It is less verbose: nothing is logged to syslog, as far as I can see.
Ok, it logs one line: <3.6> 2021-08-16 00:33:54 minas-tirith systemd 1 - - Started fetching news messages spool hourly. ... <3.6> 2021-08-16 00:39:01 minas-tirith systemd 1 - - Started fetching news messages spool hourly. ... <3.6> 2021-08-16 00:44:09 minas-tirith systemd 1 - - Started fetching news messages spool hourly. ... <3.6> 2021-08-16 00:49:59 minas-tirith systemd 1 - - Started fetching news messages spool hourly. ... <3.6> 2021-08-16 00:55:09 minas-tirith systemd 1 - - Started fetching news messages spool hourly. Not very accurate, is it? Six minutes the last one. 00:33:54 00:39:01 05:07 00:44:09 05:08 00:49:59 05:50 00:55:09 05:10 But that means it runs every 6 minutes, instead of the five I asked. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 15/08/2021 13.11, Andrei Borzenkov wrote:
On 15.08.2021 12:24, Per Jessen wrote:
Carlos E. R. wrote:
The only way to avoid it is to remove pam_systemd from crond pam config.
It is not there... minas-tirith:~ # grep -i system /etc/pam.d/crond minas-tirith:~ # -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Carlos E. R. wrote:
On 15/08/2021 13.11, Andrei Borzenkov wrote:
On 15.08.2021 12:24, Per Jessen wrote:
Carlos E. R. wrote:
The only way to avoid it is to remove pam_systemd from crond pam config.
It is not there...
minas-tirith:~ # grep -i system /etc/pam.d/crond
It's in /etc/pam.d/common-session-pc -- Per Jessen, Zürich (28.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
On 15/08/2021 14.22, Per Jessen wrote:
Carlos E. R. wrote:
On 15/08/2021 13.11, Andrei Borzenkov wrote:
On 15.08.2021 12:24, Per Jessen wrote:
Carlos E. R. wrote:
The only way to avoid it is to remove pam_systemd from crond pam config.
It is not there...
minas-tirith:~ # grep -i system /etc/pam.d/crond
It's in /etc/pam.d/common-session-pc
Changing that would not affect only cron. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Andrei Borzenkov wrote:
On 15.08.2021 12:24, Per Jessen wrote:
Carlos E. R. wrote:
Is there some way to reduce that to nothing, or at least one or two lines?
I was going to say - look at your systemd loglevel, but I don't see all that output on a couple of Leap and TW systems I have just looked at.
And you run jobs from within root crontab as different user? I most certainly do see it when running as non-root.
Yep, on my TW system I even added a job just to test: /etc/cron.d/user-per * * * * * per /bin/true
The only way to avoid it is to remove pam_systemd from crond pam config.
Hmm. Weird. -- Per Jessen, Zürich (28.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland.
On 15.08.2021 15:17, Per Jessen wrote:
Andrei Borzenkov wrote:
On 15.08.2021 12:24, Per Jessen wrote:
Carlos E. R. wrote:
Is there some way to reduce that to nothing, or at least one or two lines?
I was going to say - look at your systemd loglevel, but I don't see all that output on a couple of Leap and TW systems I have just looked at.
And you run jobs from within root crontab as different user? I most certainly do see it when running as non-root.
Yep, on my TW system I even added a job just to test:
/etc/cron.d/user-per * * * * * per /bin/true
You are already logged in, so systemd user instance is already started and active.
The only way to avoid it is to remove pam_systemd from crond pam config.
Hmm. Weird.
Andrei Borzenkov wrote:
On 15.08.2021 15:17, Per Jessen wrote:
Andrei Borzenkov wrote:
On 15.08.2021 12:24, Per Jessen wrote:
Carlos E. R. wrote:
Is there some way to reduce that to nothing, or at least one or two lines?
I was going to say - look at your systemd loglevel, but I don't see all that output on a couple of Leap and TW systems I have just looked at.
And you run jobs from within root crontab as different user? I most certainly do see it when running as non-root.
Yep, on my TW system I even added a job just to test:
/etc/cron.d/user-per * * * * * per /bin/true
You are already logged in, so systemd user instance is already started and active.
Ah, yes. Yep, with another user, I also get all the stuff. -- Per Jessen, Zürich (29.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Content-ID: <d7cdc6a-43e2-3783-a86e-82c660392945@minas-tirith.valinor> El 2021-08-15 a las 16:11 +0300, Andrei Borzenkov escribió:
On 15.08.2021 15:17, Per Jessen wrote:
Andrei Borzenkov wrote:
...
Yep, on my TW system I even added a job just to test:
/etc/cron.d/user-per * * * * * per /bin/true
You are already logged in, so systemd user instance is already started and active.
Ah! Then, if I keep a terminal logged in, it would be less verbose :-? <3.6> 2021-08-15 15:25:01 minas-tirith systemd 1 - - Created slice User Slice of UID 9. <3.6> 2021-08-15 15:25:01 minas-tirith systemd 1 - - Starting User Runtime Directory /run/user/9... <3.6> 2021-08-15 15:25:01 minas-tirith systemd 1 - - Started User Runtime Directory /run/user/9. <3.6> 2021-08-15 15:25:01 minas-tirith systemd 1 - - Starting User Manager for UID 9... <10.6> 2021-08-15 15:25:01 minas-tirith systemd - - - pam_unix(systemd-user:session): session opened for user news by (uid=0) <3.6> 2021-08-15 15:25:01 minas-tirith systemd 6329 - - Listening on Multimedia System. <3.6> 2021-08-15 15:25:01 minas-tirith systemd 6329 - - Listening on Sound System. <3.6> 2021-08-15 15:25:01 minas-tirith systemd 6329 - - Starting D-Bus User Message Bus Socket. <3.6> 2021-08-15 15:25:01 minas-tirith systemd 6329 - - Listening on D-Bus User Message Bus Socket. <3.6> 2021-08-15 15:25:01 minas-tirith systemd 1 - - Started User Manager for UID 9. <3.6> 2021-08-15 15:25:01 minas-tirith systemd 1 - - Started Session 68 of user news. <10.6> 2021-08-15 15:25:01 minas-tirith cron 6327 - - pam_unix(crond:session): session opened for user news by (uid=0) <10.6> 2021-08-15 15:25:03 minas-tirith CRON 6327 - - pam_unix(crond:session): session closed for user news <3.6> 2021-08-15 15:25:13 minas-tirith systemd 1 - - user-runtime-dir@9.service: Unit not needed anymore. Stopping. <3.6> 2021-08-15 15:25:13 minas-tirith systemd 1 - - Stopping User Manager for UID 9... <3.6> 2021-08-15 15:25:13 minas-tirith systemd 6329 - - Closed Sound System. <3.6> 2021-08-15 15:25:13 minas-tirith systemd 6329 - - Closed Multimedia System. <3.6> 2021-08-15 15:25:13 minas-tirith systemd 6329 - - Closed D-Bus User Message Bus Socket. <3.6> 2021-08-15 15:25:13 minas-tirith systemd 6329 - - Reached target Shutdown. <3.6> 2021-08-15 15:25:13 minas-tirith systemd 6329 - - Starting Exit the Session... <3.6> 2021-08-15 15:25:13 minas-tirith systemd 6329 - - Received SIGRTMIN+24 from PID 6340 (kill). <10.6> 2021-08-15 15:25:13 minas-tirith systemd - - - pam_unix(systemd-user:session): session closed for user news <3.6> 2021-08-15 15:25:13 minas-tirith systemd 1 - - user-runtime-dir@9.service: Unit not needed anymore. Stopping. <3.6> 2021-08-15 15:25:13 minas-tirith systemd 1 - - Stopped User Manager for UID 9. <3.6> 2021-08-15 15:25:13 minas-tirith systemd 1 - - user-runtime-dir@9.service: Unit not needed anymore. Stopping. <3.6> 2021-08-15 15:25:13 minas-tirith systemd 1 - - user-9.slice: Unit not needed anymore. Stopping. <3.6> 2021-08-15 15:25:13 minas-tirith systemd 1 - - Stopping User Runtime Directory /run/user/9... <3.6> 2021-08-15 15:25:14 minas-tirith systemd 1 - - Stopped User Runtime Directory /run/user/9. <3.6> 2021-08-15 15:25:14 minas-tirith systemd 1 - - user-9.slice: Unit not needed anymore. Stopping. <3.6> 2021-08-15 15:25:14 minas-tirith systemd 1 - - Removed slice User Slice of UID 9. Just a little bit less verbose. - -- Cheers Carlos E. R. (from openSUSE Leap 15.2 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCYRkXbRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcITwA/jRhTNgQjjQLa32UERIb KiRjfHY2kj2KnvbWY4TJ7R6rAP9hNFQ7uwwf8xgHzrj+125Eo96OswY+C/xh2JN9 /hRv/Q== =Hreg -----END PGP SIGNATURE-----
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
Carlos E.R. -
Per Jessen -
Yamaban