Score:0

clamdscan: Log verbose output to configurable file

cn flag

When using clamdscan, I would like to have verbose output logged to a file. Specifically, the timestamp, file path and file name as well as the scan results should be logged to a specified file. At the moment it is logged to /var/log/clamd.scan. However, given that I would like to use it within a script, I would like to log this kind of output to a configurable file.

While there is a -L switch, it does not include such detailed information (only the summary). Also, there seems to be a --stdout switch but it seems it does not help either.

How can I get verbose information from /var/log/clamd.scan to a configurable file in the first place?

Interestingly, the behavior seems to be different compared to clamscan, which outputs verbose details by default to stdout so you can pipe it to tee $LOG_FILE.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.