CustomBuild 1.1.27 and 1.2.21 brings ClamAV support!

Well have clamav in custombuild is just nice for automatization, ofc you wrote a guide and your script does alraedy that.. but... for who didnt use just a one-command line would be very helpful i suppose.

I used to install via update.script that is the same as custombuild.. just for dont have to write in the script all the steps for get it installed.

From my understanding, in future versions it will just be a matter of uncommenting one line for SA and ClamAV if you choose to use it. In my opinion, that is the way it should work.
Click to expand...

I dont get this, you mean new versions of your script or custombuild?

Ofc if is your script is up to you choose how make it work i was just giving my 2 cents :)

On my side i dont see for now a valid reason for dont install clamav and/or spamassassin so i dont need that kind of choise. Ofc, in your case, the perl part is the best way for doing it :) But ive my customized exim file that would work for any default installtion (or my own custom if is better to say) that i do.

Best regards
 
It is very easy to build support into the FTP daemons for ClamAV - maybe that should be documented/available in custom build.
 
Yes, it's very easy to do that with both Pure-ftpd and ProFTPd. How-to's will be posted on the forums or DA knowledgebase very soon.
 
smtalk: can you explain what the benefits are of your way of connecting to ClamAV from Exim? Why do you want to use TCP instead of the built in unix socket?
 
getUP said:
smtalk: can you explain what the benefits are of your way of connecting to ClamAV from Exim? Why do you want to use TCP instead of the built in unix socket?
Click to expand...

Why we shouldn't use it? ClamAV integration with FTP daemons requires a TCP socket connection to be available, and if TCP is already activated, why should we use another way of integrating it with exim?
 
smtalk said:
Why we shouldn't use it? ClamAV integration with FTP daemons requires a TCP socket connection to be available, and if TCP is already activated, why should we use another way of integrating it with exim?
Click to expand...

I'm not implying you should use another method of connecting to ClamAV. I was just wondering why you had chosen to use TCP instead of the unix socket we were used to.

Thanks for your explanation.
 
getUP said:
I'm not implying you should use another method of connecting to ClamAV. I was just wondering why you had chosen to use TCP instead of the unix socket we were used to.

Thanks for your explanation.
Click to expand...

You are welcome :) You can still use the way you were used to.
 
Hi Martynas,

when I installed ClamAV using custombuild, it doesn't start clamd.
Nor does it show any log message anywhere I could find.

Here's the last lines from the custombuild installment:
make[2]: Leaving directory `/usr/local/directadmin/custombuild/clamav-0.97.2'
make[1]: Leaving directory `/usr/local/directadmin/custombuild/clamav-0.97.2'
Restarting freshclam.
cat: /var/run/clamd.pid: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Restarting clamd.
cat: /var/run/clamd.pid: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Restarting exim.
Shutting down exim:
Starting exim:
Done ClamAV.
Click to expand...

Do you have any ideas ?
 
Please post the the result of:
Code: 
/etc/init.d/clamd start
ps aux | grep clam
 
[root@server custombuild]# /etc/init.d/clamd start
[root@server custombuild]# ps aux | grep clam
clamav 3242 0.0 0.0 39892 1412 ? Ss 2010 8:10 /usr/local/bin/freshclam -d -c 24
root 17426 0.0 0.0 61324 788 pts/0 S+ 21:26 0:00 grep clam
[root@server custombuild]#
 
@Duboux

If you need some hands to fix it for you, send me a PM, for some dollars I'll do the job. Otherwise you need to read logs or use strace.
 
Thank you for the offer zEitEr,

But as I was feeling custombuild is SM's child, he'd want to have a learning curve at any "side effects" it would produce. ;)

SM, lemme know if you want to look into this or not.

Thanks :)
 
Not at all.

Note, that in your case something seems to be mis-configured, as clamd is not running. And if so, then that is needed to do some debugging work, and it really has little with custombuild, since custombuild only installs clamav, and if you've modified something on your server that breaks clamav to run properly, nobody would know what it is exactly.
 
Duboux said:
Thank you for the offer zEitEr,

But as I was feeling custombuild is SM's child, he'd want to have a learning curve at any "side effects" it would produce. ;)

SM, lemme know if you want to look into this or not.

Thanks :)
Click to expand...

Please contact me on any instant messenger or send me a PM. I am sure it's not an issue of the CustomBuild script, but will check it for free. Probably you had an earlier manual installation of ClamAV, hadn't you?
 
thanks both.

And yes Martynas, I had a previous version installed, which I removed before I installed it via custombuild :)

I'm trying to contact u on msn/skype but as always to me, u appear offline, hehe ;)

Thanks in advance :)
 
The fix to this problem was:
Code: 
wget -O /etc/init.d/clamd files.directadmin.com/services/custombuild/clamd
wget -O /etc/init.d/freshclam files.directadmin.com/services/custombuild/freshclam
/etc/init.d/clamd restart

The server had start/stop scripts from an earlier installation of ClamAV.
 
If you install it from YUM, then YUM will install it's own ClamAV start/stop scripts, which may or may not work as well as the start/stop scripts used by DirectAdmin. You'll need to study them to see if they do what you want them to do.

Jeff
 
You must log in or register to reply here.
Back
Top