Re: multiscreen logging

2016-07-28 Thread David Kahles
Hi, Am Donnerstag, 28. Juli 2016 12:23:56 CEST schrieb Sebastian Kügler: On donderdag 28 juli 2016 01:18:00 CEST David Kahles wrote: I think the problem with this approach is, that most (or even all?) of these processes aren't units but simple processes. A better approach using the power of jour

Re: multiscreen logging

2016-07-28 Thread Sebastian Kügler
On donderdag 28 juli 2016 01:18:00 CEST David Kahles wrote: > I think the problem with this approach is, that most (or even all?) of > these processes aren't units but simple processes. > A better approach using the power of journald would be something like: > > journalctl -b --user _COMM=plasmash

Re: multiscreen logging

2016-07-28 Thread Sebastian Kügler
On woensdag 27 juli 2016 13:45:14 CEST Martin Klapetek wrote: > On Wed, Jul 27, 2016 at 7:35 AM, Sebastian Kügler wrote: > > On dinsdag 26 juli 2016 19:44:11 CEST Martin Klapetek wrote: > > On Tue, Jul 26, 2016 at 8:03 AM, Sebastian Kügler wrote: > > > > What do you think? If you like the idea,

Re: multiscreen logging

2016-07-27 Thread David Kahles
Hi, Am Mittwoch, 27. Juli 2016 22:44:38 CEST schrieb Mark Gaiser: On Tue, Jul 26, 2016 at 3:09 PM, Mark Gaiser wrote: On Tue, Jul 26, 2016 at 2:03 PM, Sebastian Kügler wrote: Hey, [Please keep both lists addressed.] Debugging multiscreen issues is a nightmare: - there are at least 4 dif

Re: multiscreen logging

2016-07-27 Thread Mark Gaiser
On Tue, Jul 26, 2016 at 3:09 PM, Mark Gaiser wrote: > On Tue, Jul 26, 2016 at 2:03 PM, Sebastian Kügler wrote: > >> Hey, >> >> [Please keep both lists addressed.] >> >> Debugging multiscreen issues is a nightmare: >> >> - there are at least 4 different processes involved (kded, kcmshell / >> s

Re: multiscreen logging

2016-07-27 Thread Martin Klapetek
On Wed, Jul 27, 2016 at 7:35 AM, Sebastian Kügler wrote: > On dinsdag 26 juli 2016 19:44:11 CEST Martin Klapetek wrote: > > On Tue, Jul 26, 2016 at 8:03 AM, Sebastian Kügler wrote: > > > > What do you think? If you like the idea, I'll polish up my branch and > will > > post it for review, so we

Re: multiscreen logging

2016-07-27 Thread Sebastian Kügler
On woensdag 27 juli 2016 17:14:21 CEST Bhushan Shah wrote: > I wonder if code is failsafe in case of such clash while opening > logfile? Because for sure, we don't want another crashes.. I don't see how it would crash. -- sebas http://www.kde.org | http://vizZzion.org ___

Re: multiscreen logging

2016-07-27 Thread Bhushan Shah
On Wed, Jul 27, 2016 at 01:35:22PM +0200, Sebastian Kügler wrote: > > Potentially, yes. Is it a problem? No. > > The log file isn't critical, and *usually* components are able to write in > order (appending to a file doesn't take long). If the log ends up being > slightly corrupted, that's bad

Re: multiscreen logging

2016-07-27 Thread Sebastian Kügler
On dinsdag 26 juli 2016 19:44:11 CEST Martin Klapetek wrote: > On Tue, Jul 26, 2016 at 8:03 AM, Sebastian Kügler wrote: > Hey, > > [Please keep both lists addressed.] > > Debugging multiscreen issues is a nightmare: > > - there are at least 4 different processes involved (kded, kcmshell / > s

Re: multiscreen logging

2016-07-26 Thread Martin Klapetek
On Tue, Jul 26, 2016 at 8:03 AM, Sebastian Kügler wrote: > Hey, > > [Please keep both lists addressed.] > > Debugging multiscreen issues is a nightmare: > > - there are at least 4 different processes involved (kded, kcmshell / > systemsettings, kscreen_backend_launcher and plasmashell) > - some

Re: multiscreen logging

2016-07-26 Thread Mark Gaiser
On Tue, Jul 26, 2016 at 2:03 PM, Sebastian Kügler wrote: > Hey, > > [Please keep both lists addressed.] > > Debugging multiscreen issues is a nightmare: > > - there are at least 4 different processes involved (kded, kcmshell / > systemsettings, kscreen_backend_launcher and plasmashell) > - some