On 04/12/2018 15.44, Peter Suetterlin wrote:
Carlos E. R. wrote:
On 02/12/2018 21.22, Andrei Borzenkov wrote:
stdout/stderr are setup in display manager and inherited by all started processes (including X server), unless processes explicitly change them. Both gdm and sddm prefer journal and this is hardcoded.
Ah. I read about this inheriting, but wasn't sure where it comes from. So starting an X session without a DM should not show that behavior? Have to try that...
Now I understand the issue.
Same here.
Systemd is innocent this time ;-)
But don't forget about the kitten!
<https://youtu.be/qiPGvvcE3wQ?t=107> X-)
Apparently, I have kstars in my older laptop, so I tried - but I do not see entries in syslog. I did not go past the introduction, though, something failed. Oh, no, my mistake: I started it remotely via ssh session, so the output is in my ssh client terminal. I'll try later locally.
I just tried at my computer at home that still runs Leap 42.3. There nothing ends up in syslog. But it's also a very old version of kstars (2.7.6 vs. now recent 3.0.0pre on my TW machine).
I tried on the same laptop as previously, but this time locally (it runs Leap 15.0, and DM=sddm), and yes, a lot of entries appeared on the system log. However, using a syslog daemon you could filter out all that crap. With the journal you can't, it will flood and rotate fast. Or fill the disk. It appears to be using facility 1 (LOG_USER) at several levels. Now, if it used a local level, it would be easier. And of course, other graphical programs may do the same. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)