--nextPart2347994.OgdKQVN5n8 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii"; protected-headers="v1" From: Kevin Ottens To: kde-frameworks-devel@kde.org, David Faure Subject: Re: Re KIO workers Date: Sun, 06 Jun 2021 01:15:35 +0200 Message-ID: <9915481.8SY5QgRo98@wintermute> In-Reply-To: <8848214.rMLUfLXkoz@asterixp15> References: <3125182.44csPzL39Z@vkpc5> <4617196.JRvLLyNDWf@wintermute> <8848214.rMLUfLXkoz@asterixp15> Hello, On Saturday, 5 June 2021 22:01:54 CEST David Faure wrote: > On samedi 5 juin 2021 21:07:39 CEST Kevin Ottens wrote: > > On Saturday, 5 June 2021 17:51:18 CEST David Faure wrote: > > > On samedi 5 juin 2021 16:29:10 CEST Volker Krause wrote: > > > > Do KIO slaves still need the klauncher/kinit loading mechanism? > > > > > > No. My request for developers to test KIO_FORK_SLAVES=1 > > > for daily use is so that apps fork kio worker processes directly, > > > without going via klauncher/kinit. BTW it seems to work fine. I wonder > > > if we should toggle that in 5.84, as part of the incremental move to the > > > KF6 world. > > > > Actually it works so well that I almost forgot I turned KIO_FORK_SLAVES > > on... > > I hope we're both wrong: the env var is *KDE*_FORK_SLAVES :) I forgot it so well that I got the variable wrong under the influence of your email. Yes, I got KDE_FORK_SLAVES enabled... went and check since you gave me a doubt. :-D Cheers. -- Kevin Ottens, http://ervin.ipsquad.net enioka Haute Couture - proud patron of KDE, https://hc.enioka.com/en --nextPart2347994.OgdKQVN5n8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQQXFmpSdcX6bxpI/XgHS7vLjezJ4gUCYLwFlwAKCRAHS7vLjezJ 4p/KAKCs5jN11z68lEvjEkq88jUPfdOBVgCePdxvdI6Y6qcCdp71lrf6cWLtuuo= =yjfV -----END PGP SIGNATURE----- --nextPart2347994.OgdKQVN5n8--