O systemd-logind deve estar rodando no container do docker?

0

Eu quero saber, o systemd-logind deve estar em execução no contêiner docker? O systemd-logind do meu contêiner sempre consome CPU 100% e o efeito do systemd-logind?

Se eu parar o systemd-logind do docker container para sempre, haverá outras influências?

    
por 穆阿浩 01.06.2017 / 11:22

1 resposta

0

Depende realmente da distribuição do linux que você usa como modelo do Docker, mas isso não explica os 100%.

O Systemd-logind não deve usar tanto CPU como o trabalho:

https://www.freedesktop.org/software/systemd/man/systemd-logind.service.html

systemd-logind is a system service that manages user logins. It is responsible for:

Keeping track of users and sessions, their processes and their idle state. This is implemented by allocating a systemd slice unit for each user below user.slice, and a scope unit below it for each concurrent session of a user. Also, a per-user service manager is started as system service instance of [email protected] for each user logged in.

Generating and managing session IDs. If auditing is available and an audit session ID is set for a session already, the session ID is initialized from it. Otherwise, an independent session counter is used.

Providing PolicyKit-based access for users to operations such as system shutdown or sleep

Implementing a shutdown/sleep inhibition logic for applications

Handling of power/sleep hardware keys

Multi-seat management

Session switch management

Device access management for users

Automatic spawning of text logins (gettys) on virtual console activation and user runtime directory management

Suponho que há algo errado com seu modelo de janela de encaixe.

    
por 01.06.2017 / 11:39

Tags