4
edits
Difference between revisions of "ClamAV"
Setup via CLI: Services : added check for cron daemon
(Proposal: Update - reorganization of the structure) Tags: Mobile web edit Mobile edit |
(Setup via CLI: Services : added check for cron daemon) |
||
| Line 57: | Line 57: | ||
<!--T:13--> | <!--T:13--> | ||
You may get a notification that <code>clamd</code> was not notified. This is normal because we haven't started the service yet. | You may get a notification that <code>clamd</code> was not notified. This is normal because we haven't started the service yet. | ||
<!--T:18--> | |||
Check database version: | |||
<!--T:19--> | |||
<syntaxhighlight lang="shell"> | |||
freshclam --version | |||
</syntaxhighlight> | |||
== Services == | == Services == | ||
=== clamav / freshclam === | |||
<!--T:14--> | <!--T:14--> | ||
| Line 76: | Line 86: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
=== cron === | |||
Make sure a cron daemon (for example 'cronie') is installed, enabled and running, as cronjobs are used in this guide. | |||
See also: [https://wiki.archlinux.org/title/Cron Cron] | |||
Example with 'cronie' (install, enable+start and check status): | |||
<syntaxhighlight lang="shell"> | <syntaxhighlight lang="shell"> | ||
sudo pacman -S cronie | |||
sudo systemctl enable --now cronie.service | |||
sudo systemctl status cronie.service | |||
</syntaxhighlight> | </syntaxhighlight> | ||
Alternative: Use systemd Timers. See: [https://wiki.archlinux.org/title/Systemd/Timers systemd/Timers] | |||
== Schedule scans through 'cron' == <!--T:23--> | == Schedule scans through 'cron' == <!--T:23--> | ||
| Line 103: | Line 118: | ||
mkdir -p "${HOME}/.clam/quarantine" && mkdir -p "${HOME}/.clam/logs" | mkdir -p "${HOME}/.clam/quarantine" && mkdir -p "${HOME}/.clam/logs" | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Otherwise, for example, creating the logfile may fail due to missing authorization. | Otherwise, for example, creating the logfile may fail due to missing authorization. | ||