Arch Linux User Repository

Updated to 5.6.2-3 which disables Yara rules update till it is fixed upstream by extremeshok or Yara rules project. (you can still easily enable it if you want.)

Fixed systemd.timer, outdated os.conf and custom config directory bug.

Also package works out-of-box i.e. now there is no need to set: user_configuration_complete="yes" in user.conf.

Modify user.conf if you want some different settings.

Update: Removed

Also I will be removing clamd.scan.service file from the package, in future release for the following reasons:

1) It does not add much value except activating the timer. (which one can do manually one time)

2) It depends on a non-existing clamd@.service file which means that clamd.scan.service file wont work anyway.

3) Starting clamd service is not this package's business. Default clamav-daemon.service that comes with clamav should be used instead.

Updated to 5.6.2-3 which disables Yara rules update till it is fixed upstream by extremeshok or Yara rules project. (you can still easily enable it if you want.)

Fixed systemd.timer, outdated os.conf and custom config directory bug.

Also package works out-of-box i.e. now there is no need to set: user_configuration_complete="yes" in user.conf.

Modify user.conf if you want some different settings.

Thanks. I will update package by this weekend.

@amish - It's done.

I have my attention in other packages and projects, I pass you the relay.

@ValHue - yes sure thanks. :) Or may be its possible to add as co-maintainer too. So you can maintain it too

@amish:

Do you want to take charge of the maintenance of this package?

I do not dedicate the time that it deserves and I always go behind your contributions, I would not mind giving it to you.

Best regards

One or more of the yara signature databases causes a crash and coredumps of clamav 0.100.0

After deleting all yara signature databases no more crashes occurred. What I do not quite understand is that there were error messages in version 0.99.4, but it never came to coredumps and crashes. I have not yet figured out which yara database is responsible for the errors. Currently I have deactivated all yara databases and clamav is running stable.

See my Bugreport

https://bugs.archlinux.org/task/58513

clamd.service is now renamed to clamav-daemon.service. Hence, file os.conf should have:

clamd_restart_opt="systemctl restart clamav-daemon.service"

clamd_reload_opt="systemctl reload clamav-daemon.service"

clamd_socket="/run/clamav/clamd.ctl"

Also add these two lines to os.conf. So accidental overwrites to files do not happen by install commands. And it will tell users to use 'pacman' instead.

pkg_mgr="pacman"

pkg_rm="pacman"

Also WantedBy in clamav-unofficial-sigs.timer should be corrected to:

WantedBy=timers.target

Because clamd@scan is not default service. And because of that timer never starts (and database never updates) if user does not use clamd@scan service.

@amish, Thanks for your contribution.

The patch file clamav-unofficial-sigs.service.patch creates an unnecessary file with .orig extension. i.e. /usr/lib/systemd/system/clamav-unofficial-sigs.service.orig

This can be fixed by changing 27 to 22 (line number) in patch file.

But actually there is no need to use patch file at all. In PKGBUILD, replace patch call with the following sed line.

sed -i -e 's#/usr/local/s\?bin#/usr/bin#g' systemd/clamav-unofficial-sigs.service

(It will replace /usr/local/sbin and /usr/local/bin with /usr/bin anywhere in service file.)

This will eliminate any similar future issues incase .service file is changed upstream. And reduce maintenance a bit.