qual é o arquivo eipp.log.xz?

2

Eu encontrei no meu sistema de framboesa baseado no debian stretch um arquivo chamado eipp.log.xz .
Localizado em / var / log / apt / .

Eu queria saber o que é isso.

Do authlog , por volta da hora da criação, encontrei algo que talvez seja algo de "debian-security-support"?

Mar 16 06:49:18 pi su[22037]: Successful su for debian-security-support by root
Mar 16 06:49:18 pi su[22037]: + ??? root:debian-security-support
Mar 16 06:49:18 pi su[22037]: pam_unix(su:session): session opened for user debian-security-support by (uid=0)
Mar 16 06:49:19 pi systemd-logind[247]: New session c116 of user debian-security-support.
Mar 16 06:49:19 pi systemd: pam_unix(systemd-user:session): session opened for user debian-security-support by (uid=0)
Mar 16 06:49:21 pi su[22037]: pam_unix(su:session): session closed for user debian-security-support
Mar 16 06:49:21 pi systemd-logind[247]: Removed session c116.
Mar 16 06:49:22 pi su[23052]: Successful su for debian-security-support by root
Mar 16 06:49:22 pi su[23052]: + ??? root:debian-security-support
Mar 16 06:49:22 pi su[23052]: pam_unix(su:session): session opened for user debian-security-support by (uid=0)
Mar 16 06:49:22 pi systemd: pam_unix(systemd-user:session): session closed for user debian-security-support
Mar 16 06:49:22 pi systemd-logind[247]: New session c117 of user debian-security-support.
Mar 16 06:49:22 pi systemd: pam_unix(systemd-user:session): session opened for user debian-security-support by (uid=0)
Mar 16 06:49:25 pi su[23052]: pam_unix(su:session): session closed for user debian-security-support
Mar 16 06:49:26 pi systemd-logind[247]: Removed session c117.

Eu deveria estar preocupado?

thx

    
por 2IRN 17.03.2018 / 15:48

1 resposta

1

Você não precisa se preocupar, pois esse arquivo é usado pelo planejador de apt . Não tem nada a ver com debian-security-support (que também é OK, vem do pacote de mesmo nome).

eipp.log.xz faz parte do “Protocolo do Planejador de Instalação Externa”, que é uma interface entre o APT, ferramentas de planejamento externas (incluindo o próprio APT) e dpkg . Foi implementado como parte do projeto David Kalnishkies GSoC 2016 ; uma breve descrição do o commit inicial dá algumas informações:

APT-based tools like apt-get, aptitude, synaptic, … work with the user to figure out how their system should look like after they are done installing/removing packages and their dependencies. The actual installation/removal of packages is done by dpkg with the constrain that dependencies must be fulfilled at any point in time (e.g. to run maintainer scripts).

Historically APT has a super micro-management approach to this task which hasn't aged that well over the years mostly ignoring changes in dpkg and growing into an unmaintainable mess hardly anyone can debug and everyone fears to touch – especially as more and more requirements are tacked onto it like handling cycles and triggers, dealing with "important" packages first, package sources on removable media, touch minimal groups to be able to interrupt the process if needed (e.g. unattended-upgrades) which not only sky-rocket complexity but also can be mutually exclusive as you e.g. can't have minimal groups and minimal trigger executions at the same time.

Este trabalho é o que levou ao processo mais restrito de instalação e atualização que você verá nas versões atuais do APT, particularmente visível com os pacotes renomeados que você verá sendo transmitidos para dpkg , com um número de pedidos adicionado. / p>     

por 17.03.2018 / 16:06

Tags