I'm puzzled by such statements as
diff /var/clamav/daily.cvd /var/clamav/daily.cvd.rpmnew Binary files /var/clamav/daily.cvd and /var/clamav/daily.cvd.rpmnew differ
I thought the point of rpmnew files was so that we could check what has been changed?
Anne
Anne Wilson wrote:
I'm puzzled by such statements as
diff /var/clamav/daily.cvd /var/clamav/daily.cvd.rpmnew Binary files /var/clamav/daily.cvd and /var/clamav/daily.cvd.rpmnew differ
I thought the point of rpmnew files was so that we could check what has been changed?
As those are binary files, diff doesn't really work. Those are db4(?) database files, you should be able to view them with the db_dump utility. Which doesn't really matter, as those will get overwritten by the next freshclam run anyway.
Ralph
On Thu, Apr 9, 2009 at 3:39 PM, Anne Wilson cannewilson@googlemail.com wrote:
I'm puzzled by such statements as
diff /var/clamav/daily.cvd /var/clamav/daily.cvd.rpmnew Binary files /var/clamav/daily.cvd and /var/clamav/daily.cvd.rpmnew differ
I thought the point of rpmnew files was so that we could check what has been changed?
You can check to see what has been changed, since you have both versions, but you should use a tool that can compare binary files (if that makes any sense to you).
In your case, you can safely delete daily.cvd.rpmnew, because, most probable, freshclam already updated daily.cvd to a newer version.
On Thursday 09 April 2009 15:01:37 George Negoita wrote:
On Thu, Apr 9, 2009 at 3:39 PM, Anne Wilson cannewilson@googlemail.com
wrote:
I'm puzzled by such statements as
diff /var/clamav/daily.cvd /var/clamav/daily.cvd.rpmnew Binary files /var/clamav/daily.cvd and /var/clamav/daily.cvd.rpmnew differ
I thought the point of rpmnew files was so that we could check what has been changed?
You can check to see what has been changed, since you have both versions, but you should use a tool that can compare binary files (if that makes any sense to you).
In your case, you can safely delete daily.cvd.rpmnew, because, most probable, freshclam already updated daily.cvd to a newer version.
Thanks, both of you. I did wonder if it was a generated file, but couldn't see the need for the rpmnew if it was. I'll need to carefully go through the /etc/clamd.conf.rpmnew, though. A quick look tells me I've lost the mailto, so I need to check what else has changed.
Anne
On Thu, 2009-04-09 at 15:30 +0100, Anne Wilson wrote:
On Thursday 09 April 2009 15:01:37 George Negoita wrote:
On Thu, Apr 9, 2009 at 3:39 PM, Anne Wilson cannewilson@googlemail.com
wrote:
I'm puzzled by such statements as
diff /var/clamav/daily.cvd /var/clamav/daily.cvd.rpmnew Binary files /var/clamav/daily.cvd and /var/clamav/daily.cvd.rpmnew differ
I thought the point of rpmnew files was so that we could check what has been changed?
You can check to see what has been changed, since you have both versions, but you should use a tool that can compare binary files (if that makes any sense to you).
In your case, you can safely delete daily.cvd.rpmnew, because, most probable, freshclam already updated daily.cvd to a newer version.
Thanks, both of you. I did wonder if it was a generated file, but couldn't see the need for the rpmnew if it was. I'll need to carefully go through the /etc/clamd.conf.rpmnew, though. A quick look tells me I've lost the mailto, so I need to check what else has changed.
And this is where vimdiff is your best friend... ;)
-I