Centos 4.5 switching from clamscan to clamdscan?

Discussion in 'Installation/Configuration' started by mxc, Oct 8, 2007.

  1. mxc

    mxc ISPConfig Developer ISPConfig Developer

  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Please do not mix up clamscscan (clamav) and spamassassin as they are different software. If a mail is scanned for viruses, you will not see spamassassin processes as spamassassin scans for spam.
     
  3. mxc

    mxc ISPConfig Developer ISPConfig Developer

    thanks for the reply. So its ok if I do all the other steps except adding /etc/init.d/spamassasin to the default run levels?

    I used to see at least 10-20 clamav/spamassasin processes running when doing a top. Now I hardly ever see clamd showing in the processes list for top. It seems to show hardly at all.
     
    Last edited: Oct 8, 2007
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Yes, because we just changed clamd and not spamassassin to daemon mode.

    Clamd is much faster then clamscan, so you will not see the process with top very often.
     

Share This Page