나는 현재 이것을 팔로우하고 있습니다가이드그러나 ClamAV
내 컴퓨터에 설정할 때AlmaLinux 9.3
11단계부팅할 수 없으며 clamd@service
다른 소스에서 많은 정보를 찾을 수 없기 때문에 다른 사람이 이 문제를 겪었는지 궁금합니다.
[root@localhost tester]# sudo systemctl status clamd@service
× [email protected] - clamd scanner (service) daemon
Loaded: loaded (/usr/lib/systemd/system/[email protected]; disabled; preset: disabled)
Active: failed (Result: exit-code) since Thu 2023-12-28 12:08:15 GMT; 3min 26s ago
Docs: man:clamd(8)
man:clamd.conf(5)
https://www.clamav.net/documents/
Process: 6728 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/service.conf (code=exited, status=1/FAILURE)
CPU: 3ms
Dec 28 12:08:15 localhost.localdomain systemd[1]: [email protected]: Scheduled restart job, restart counter is at 5.
Dec 28 12:08:15 localhost.localdomain systemd[1]: Stopped clamd scanner (service) daemon.
Dec 28 12:08:15 localhost.localdomain systemd[1]: [email protected]: Start request repeated too quickly.
Dec 28 12:08:15 localhost.localdomain systemd[1]: [email protected]: Failed with result 'exit-code'.
Dec 28 12:08:15 localhost.localdomain systemd[1]: Failed to start clamd scanner (service) daemon.
제안된 터미널 출력을 기반으로 다음 명령을 실행했습니다.
$ journalctl -xeu [email protected]
░░ The process' exit code is 'exited' and its exit status is 1.
Dec 28 12:45:18 localhost.localdomain systemd[1]: [email protected]: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit [email protected] has entered the 'failed' state with result 'exit-code'.
Dec 28 12:45:18 localhost.localdomain systemd[1]: Failed to start clamd scanner (service) daemon.
░░ Subject: A start job for unit [email protected] has failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ A start job for unit [email protected] has finished with a failure.
░░
░░ The job identifier is 7444 and the job result is failed.
Dec 28 12:45:18 localhost.localdomain systemd[1]: [email protected]: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ Automatic restarting of the unit [email protected] has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 28 12:45:18 localhost.localdomain systemd[1]: Stopped clamd scanner (service) daemon.
░░ Subject: A stop job for unit [email protected] has finished
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ A stop job for unit [email protected] has finished.
░░
░░ The job identifier is 7568 and the job result is done.
Dec 28 12:45:18 localhost.localdomain systemd[1]: [email protected]: Start request repeated too quickly.
Dec 28 12:45:18 localhost.localdomain systemd[1]: [email protected]: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit [email protected] has entered the 'failed' state with result 'exit-code'.
Dec 28 12:45:18 localhost.localdomain systemd[1]: Failed to start clamd scanner (service) daemon.
░░ Subject: A start job for unit [email protected] has failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ A start job for unit [email protected] has finished with a failure.
░░
░░ The job identifier is 7568 and the job result is failed.
답변1
콘텐츠 /etc/clamd.d/scan.conf
를 /etc/clamd.d/service.conf
파일에 복사하고 11단계에서 수정합니다.
그들이 호출하는 systemd 단위에는 인스턴스 이름이 있으며, @
이는 변수에 단위로 전달되고 로 참조됩니다 %i
. 따라서 호출하려고 하면 존재하지 않는 모든 유닛 파일을 systemctl start clamd@service
참조하게 됩니다 ./etc/clamd.d/service.conf
장치가 찾고 있는 프로필을 생성하면 시작되어야 합니다.
참고로 유닛파일은/usr/lib/systemd/system/[email protected]