-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClamAV 1.0.7: clamd on Ubuntu 24.04.1 (LTS) ignores own clamd settings #1394
Comments
as you can see and compare: My clamd(-daemon).log: Sun Oct 27 20:15:29 2024 -> +++ Started at Sun Oct 27 20:15:29 2024 My clamd.conf: LogFileUnlock yes User clamav TCPAddr 127.0.0.1 TemporaryDirectory /tmp LocalSocketGroup clamav You see, a lot of my settings are not in the log-file, not sure if it will have effect then. |
Depending on how you install clamav, the config path and database paths will be different. If you're installing clamav from a linux package distribution, (e.g "apt install") then you will also get a default clamd config and the paths will be like:
If you install from source, or use the clamav team provided RPM or DEB packages to install, then you won't get a default config and the paths will be like:
So if you install with apt-get, and then go put a config file in the other place, the apt-get installed clamd won't find it. |
Run |
here the log of $ clamconf -n Config file: clamd.confLogFile = "/var/log/clamav/clamd-daemon.log" Config file: freshclam.confLogFileMaxSize = "4294967295" clamav-milter.conf not found Software settingsVersion: 1.0.7 Database informationDatabase directory: /var/lib/clamav Platform informationuname: Linux 6.8.0-47-generic #47-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 21:40:26 UTC 2024 x86_64 Build informationGNU C: 13.2.0 (13.2.0) |
okay when i see this right, clamd takes my settings but the default log prints wrong settings, right? |
It seems that clamd-deamon don't accept my settings and loads always it's defaults.
Only some own changes will have effect.
When i use some settings from your own clamd.example, which is not implemented in my Clam Version, the whole Process breaks down or never start. This is not really nice handling for such cases. If the user use an obsolete setting, you do logging and ignore it, that's great, but why not if an option isn't included in the current Version of the User?
The text was updated successfully, but these errors were encountered: