On 02/12/2014 10:52 PM, Slávek Banko wrote:
On Thursday 13 of February 2014 03:13:02 Slávek Banko wrote:
On Thursday 13 of February 2014 01:48:38 David C. Rankin wrote:
On 02/10/2014 09:55 PM, David C. Rankin wrote:
On 02/10/2014 08:14 PM, Slávek Banko wrote:
Currently I have unfinished a patch for kdesktop_lock => response to systemd signals Lock(), Unlock() and setting SetIdleHint(true / false). I'll put patch to test when will be ready.
Then I want to prepare minimal systemd support for TDM.
And as a last I want to deal with automatic MultiSeat with systemd. But I would like to use D-Bus calls instead of a direct call API functions sd_*.
Excellent. Just let me know when you want me to test. Thanks.
Slavek,
We may need to bump priority on this one - it is worse than initially reported. It doesn't just effect fringe tdeio_slaves like the sftp tdeio_slave it effects *ALL* tdeio_slaves, including tdeio_http. I browsed in konqueror looking for configuration help with Tork and for help with the mixminion python error and I had 50+ tdeio_file and tdeio_http processes like the following:
... tdeio_file [tdeinit] file /tmp/tdesocket-david/tdelauncher0fCUxj.s tdeio_file [tdeinit] file /tmp/tdesocket-david/tdelauncher0fCUxj.s tdeio_file [tdeinit] file /tmp/tdesocket-david/tdelauncher0fCUxj.s tdeio_http [tdeinit] https /tmp/tdesocket-david/tdelauncher0fCUxj. tdeio_http [tdeinit] https /tmp/tdesocket-david/tdelauncher0fCUxj. ...
Apparently with every http connection, including browser search, a tdeio_file slave is also opened to check/update the cache entries in addition to the tdeio_http slave opened for the connection, so this will spin out of control quickly with internet browsing.
I am not sure whether this behavior is due to session management. That is very reminds me the bug report 1656.
http://bugs.trinitydesktop.org/show_bug.cgi?id=1656
However, it does not change the fact that I'll continue to work to supplement sytemd support. Unfortunately, I have in recent days been too busy with my work tasks.
Slavek
The first part for the test:
Into kdesktop is added dBus connection and response to SystemD signals Lock() and Unlock() - true, on Unlock() is nothing performed. At the same time on activate / deactivate the screen saver is called SetIdleHint(true / false).
Slavek
Excellent, I'll rebuild and report back.