Clamd can't start if clamd.conf contains inline comments

[Julien Mailleret]

Describe the bug

Clamd start is failing when some comment are added on the same line as a config value in the clamd.conf file.

How to reproduce the problem

Edit clamd.conf and add MaxRecursion 20 # set to 20 for example.

$ grep MaxRecursion /etc/clamav/clamd.conf
MaxRecursion 20 # set to 20
$ clamd
ERROR: Incorrect argument format for option MaxRecursion
ERROR: Can't open/parse the config file /etc/clamav/clamd.conf

Move the inline comment to its own line and it's starting again:

$ grep -B1 MaxRecursion /etc/clamav/clamd.conf
# set to 20
MaxRecursion 20
$ clamd
$ echo $?
0
$ ps -ef | grep clamd | grep -v grep
  121 clamav    0:16 {clamd} /run/rosetta/rosetta /usr/sbin/clamd clamd

Attachments

If applicable, add screenshots to help explain your problem.

If the issue is reproducible only when scanning a specific file, attach it to the ticket.

[Micah Snyder]

I agree, it would be nice if clamav's config files would support inline comments.