Bug 859339 - Clamdscan hardcoded to /etc/clamd.conf config
Clamdscan hardcoded to /etc/clamd.conf config
Status: ASSIGNED
Product: Fedora
Classification: Fedora
Component: clamav (Show other bugs)
25
x86_64 Linux
medium Severity low
: ---
: ---
Assigned To: Sergio Monteiro Basto
Fedora Extras Quality Assurance
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-21 04:26 EDT by Arthur Dent
Modified: 2017-07-17 08:48 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-08-01 01:36:14 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Arthur Dent 2012-09-21 04:26:12 EDT
Description of problem:

Using clamdscan instaslled from yum and properly configured, it appears that it is hard-coded to look for its config file in /etc/clamd.conf whereas since the advent of systemd the config is now actually /etc/clamd.d/scan.conf

Version-Release number of selected component (if applicable):
TBC

How reproducible:
Always

Steps to Reproduce:
1. Do a fresh and clean install (using yum) of clamav-server-systemd, clamav-scanner-systemd and all their dependencies.

2. Configure /etc/clamd.d/scan.conf to get a working clamd system

3. Run (e.g.) # clamdscan -V (as root)
  
Actual results:
ERROR: Can't parse clamd configuration file /etc/clamd.conf

Expected results:
Echo current clamav version number to terminal

Additional info:
A work-around to get this working is either to do:
# clamdscan -c /etc/clamd.d/scan.conf -V ; or
symlink /etc/clamd.conf to /etc/clamd.d/scan.conf

Either fo these two methods seem like a kludge and should not be required.

Unless I am missing some hidden configuration, it seems that clamdscan is hard-coded to look for the config in /etc/clamd.conf.

Zdenek Pytela in this thread:
http://lists.fedoraproject.org/pipermail/users/2012-September/424666.html
(specifically in this post: http://lists.fedoraproject.org/pipermail/users/2012-September/424871.html)

agrees that it does seem to be hard-coded:

strings /bin/clamdscan
...
/etc/clamd.conf
...
or
strace -e open,stat -o /tmp/clamscan.strace clamdscan -V
...
open("/etc/clamd.conf", O_RDONLY)       = -1 ENOENT (No such file or directory)
...
Comment 1 Fedora Admin XMLRPC Client 2013-02-27 16:06:36 EST
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 2 Fedora End Of Life 2013-07-03 21:17:45 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2013-08-01 01:36:19 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 4 Gerald Cox 2017-02-20 08:28:10 EST
Reopening... experiencing this issue with F25.
Comment 5 Fedora Admin XMLRPC Client 2017-03-27 13:21:11 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 6 Fedora Admin XMLRPC Client 2017-07-12 22:21:17 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 7 Fedora Admin XMLRPC Client 2017-07-17 08:48:22 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Note You need to log in before you can comment on or make changes to this bug.