>"Dennis Peterson" <[EMAIL PROTECTED]> wrote in message >news:[EMAIL PROTECTED] >> Ken Morley wrote: >>> I've installed ClamAV on RedHat ES3 many times without issue. This is >>> my first installation on SuSE Linux Enterprise Server 9 and I have to >>> use many configure switches just to get the file paths to come out >>> right. I'm not sure if the problem is due to ClamAV version 0.88, SuSE >>> ES9 or something I'm doing wrong. >>> >>> When installing previous ClamAV versions on RedHat ES3, I would just use >>> ./configure with no switches and everything would end up where I wanted >>> it: clamd.conf in /etc, the defininition files in /var/lib/clamav, etc. >>> Doing the same (prior version of ClamAV though) on SuSE ES9 yields >>> clamd.conf in /usr/local//etc. >>> >>> I have to use the following to get everything where I want it: >>> >>> ./configure --datadir=/var/lib/clamav --sysconfdir=/etc --disable-clamav >>> --with-user=amavis --with-group=amavis --sharedstatedir=/var/lib/clamav >>> --localstatedir=/var/lib/clamav --prefix=/ --with-dbdir=/var/lib/clamav >>> >> >> This is absolutely normal and is an expected activity for anyone who >> builds ClamAV whom also does not wish to or cannot use the defaults. That >> is the only reason these options are available. They empower you to >> personally manage your builds and upgrades. It's a good thing - be happy. >> >> Put what you have done above in a build script and keep it around for >> your future upgrades and you will always have predictable builds. I use >> buildit.sh scripts for absolutely everything from Apache to Zend because >> I prefer consistency over easy. Otherwise one is left to the whim of the >> vendors (not just ClamAV) who may change defaults (which are arbitrary >> values in most cases) with little or no notice, or your own memory of how >> you built the previous version. Consider it a configuration management >> tool. >> >> dp >> _______________________________________________ >> http://lurker.clamav.net/list/clamav-users.html >> Dennis:
Thanks for your response. I certainly appreciate the power and flexibility that the command-line switches provide. My question was really more about "what changed to make the installation behave differently". I think that I've got the answer. My curiosity got the better of me, so I setup a RHES 3 system from scratch, downloaded and installed ClamAV 0.88, etc. I can run ./configure with no switches and it will default to the file paths I want. That's clamd.conf in /etc, binaries in /usr/local/bin and /usr/local/sbin, etc. As soon as I supply any command-line switch (eg: --with-usr=amavis), then the default file paths all change (eg: clamd.conf will be placed in /usr/local/etc), unless of course I specify each of the directories with a switch. I didn't expect that behavior. I thought that specifying a command-line switch would change just that one setting from the default. That's not what's happening. If you specify any switches, you better specify *all* of them, because *all* of the defaults change. I was very used to just installing without using any switches and having everything placed exactly where it should be. In this case, specifying --with-user=amavis changes everything dramatically. Thanks! _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
