Sandy Drobic wrote:
Hylton Conacher (ZR1HPC) wrote:
Hi Sandy,
Thanks for the freebie info so far. It is much appreciate and its great to have someone of your superior knowledge assisting me.
The problem is, that I do not know what and how to do the system config to give me a system like you describe.
I think I already posted the relevant parts of the config files a few days ago. Okay, I just saw, that I posted EVERYTHING necessary to do the job.
Now, before you start to mangle your system, a few words of caution:
- as a beginner you should ensure you can retrace your steps if something breaks horribly. For that reason:
I suggest you make copies of the configuration files BEFORE you change them!
Copies made with date and time in a newly created backup directory.
Another possibility is to document the changes within the configuration files like:
This I would do all the time as that way you can see what was there and when you changed it.
The necessary parts that HAVE to be present in /etc/clamd.conf are: LogTime yes LogSyslog yes LogFacility LOG_MAIL LocalSocket /var/run/clamav/clamd FixStaleSocket yes TCPSocket 3310 TCPAddr 127.0.0.1 User vscan
Apart from LocalSocket entry my conf is OK. My socket entry read '/var/lib/clamav/clamd-socket' so I changed it to what you had and created the clamav dir under /var/run/ and assigned the owner and group to vscan. Did a 'rcclamd restart' and it failed :( Below is error message: Umalusi:~ # rcclamd restart ERROR: Parse error at line 30: Option LogTime requires boolean argument. ERROR: Parse error at line 30: Option LogTime requires boolean argument. Shutting down Clam AntiVirus daemon done ERROR: Parse error at line 30: Option LogTime requires boolean argument. Starting Clam AntiVirus daemon ERROR: Parse error at line 30: Option LogTime requires boolean argument. ERROR: Can't open/parse the config file /etc/clamd.conf startproc: exit status of parent of /usr/sbin/clamd: 1 failed What now?
If necessary, create the directory and assign it to user vscan:
I needed to create the clamac directory under run and assigned it to user and group vscan.
mkdir /var/run/clamav chown -R vscan /var/run/clamav
Then restart clamd: "rcclamd restart". I consider logging parameters relevant since I like to know what the service is doing. (^-^)
Within /var/run/clamav there should now be a file clamd:
There isn't ??
If no error are logged you can set up the cron job:
IF......but there were errors that need repairing first. <rest snipped> I have reverted to the backup copy for the moment and done a rcclamd restart successfully. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org