On 31/10/2019 11:02, Lennart Poettering wrote:
> On Mi, 30.10.19 11:08, Bhasker C V (bhas...@unixindia.com) wrote:
>
>> Hi all,
>>
>> I have been googl-ing for a few days now but could not stumble upon a
>> solution I am looking for.
>>
>> Apologies if this is a noob question.
>>
>> Is there a wa
On Fri, Nov 1, 2019 at 1:49 AM Paul Davey
wrote:
> What is the best way to fix this issue? I have locally had success
> just calling the on_spawn_io callback in the process success branch of
> on_spawn_sigchld, but I am unsure if this is an acceptable fix.
In the callback, we call read() only o
On Fr, 01.11.19 08:59, Bhasker C V (bhas...@unixindia.com) wrote:
> > systemd owns the cgroup tree, only subtrees for which delegation is
> > explicitly turned on can be managed by other programs, for example for
> > the purpose of container managers.
> >
> > Thus, creating cgroups manually, direc
On 01/11/2019 09:20, Lennart Poettering wrote:
> On Fr, 01.11.19 08:59, Bhasker C V (bhas...@unixindia.com) wrote:
>
>>> systemd owns the cgroup tree, only subtrees for which delegation is
>>> explicitly turned on can be managed by other programs, for example for
>>> the purpose of container manage
On Fr, 01.11.19 09:32, Bhasker C V (bhas...@unixindia.com) wrote:
> I am really sorry but I am still not able to get this working with a
> 'name' in slice. Is there a naming convention to be used for the name
> passed-on to --slice=. I could not understand this from the man
> page.
Slices in sys
On 01/11/2019 10:03, Lennart Poettering wrote:
> On Fr, 01.11.19 09:32, Bhasker C V (bhas...@unixindia.com) wrote:
>
>> I am really sorry but I am still not able to get this working with a
>> 'name' in slice. Is there a naming convention to be used for the name
>> passed-on to --slice=. I could no
On Thu, Oct 31, 2019 at 5:06 PM Lennart Poettering
wrote:
> Paging doesn't allow that really. It's always ugly. You'd have to have
> your own UI stack in the initrd, i.e. basically have an alternative
> root disk, that possesses the screen exclusively as long as the system
> is up but not unlocked
