• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

ClamAV GUI version 2.1.0

Started by CDRWSel, 2011.02.26, 12:02:28

Previous topic - Next topic

CDRWSel

http://www.os2world.com/content/view/20595/2/
QuotePosted by Martin Iturbide - Tuesday, 22 February 2011


[a href. .. .

One more time, I'm unable to add any updates into ClamAV GUI version 2.0.0 forum entry (blank page !)

Hi Dave,

It looks like starting ClamD from config.sys makes it ignore the  "LocalSocket" which could not be initialized.
This makes Clamdscan not been able to communicate with it.
* For system protection, starting Clamd from config.sys is ok
* To use Clamdscan with Clamd, the LocalSocket must be enabled and this requires to start Clamd out of config.sys

If Clamd is added into config.sys, prefer use Clamscan or stop/re-start Clamd before use of Clamdscan
You can do like this (with rxu.dll into dll path):
- Show PIDs
- Kill Clamd process
- Verify Daemons
- Start ClamDaemon

Or, you can update startup.cmd to start clamd after eCS full initialization
I'll update docs with these restrictions.

About the clamd.conf problem you reported, I'm correcting it.
Could you please tell under which path you have clamd.conf available when installed through RPM/YUM ?
Thanks

Kind regards,
Remy

David McKenna

Hi Remy,

  OK, thanks - I'll try starting Clamd either from the startup folder or startup.cmd. RPM puts clamd.conf (and freshclam.conf) in /etc .

Regards,

Dave McKenna

CDRWSel

#2
Hello Dave,

I corrected the cond config file problem you identified.
(Now, you'll have an option to choice if original Clamd.conf exist but this one may not be configurated when using Clamdscan as scan engine or starting clamd from ClamAV-GUI at first time)

Could you please do a try of this update
http ://remydodin.levillage.org/outils/ ClamAVGUI-2_1_2.wpi

   * Changed RUN= added position into config.sys (to prevent some MPTSTART error at start time if placed as first RUN= statement)
   * Changed REM text when adding Clamd into config.sys
   * Changed process to select ClamD config file. If original Clamd.conf file exist, it is given possibility to use it instead of ClanAV-GUI configured conf file.
   * If original Clamd config file is selected to be used, "epm" opens to allow user to correct/update his config file (User has to know which parms to add to have clamdscan working too)


Please remove blanks into above link.
Kind regards,
Remy



David McKenna

Hi Remy,

  I tried your test version 2.1.2 and it seems to work as you describe. It would be nice if when using Clamdscan(conf) the software could automatically detect which conf file is in use and just open that one... don't know if that is possible. In any case having the choice is good.

  One minor thing I just noticed. After starting ClamAVGUI, when going to ClamAVGUI settings then hitting 'save' a new freshclam_GUI.conf file is created in the ClamAVGUI directory (not /etc) and the original one saved even if there are no changes. It only happens the first time after starting ClamAVGUI. Due to all my testing I had about 60 saved freshclam_GUI.conf files in my ClamAVGUI directory. I am not sure this is what you intend.

  FYI - I start ClamD from an object in the startup folder and that seems to work well with Clamdscan.

Regards,

Dave McKenna

CDRWSel

Hi Dave,

About automatic Clamd config file check, I prefered left end-user to make the "choice" because there are several must entries which could differ and may have other value than those defaults I use. This makes the verification more complex...
Using both ClamAV-GUI provided and generated config files makes ClamAV work in most configurations.     

I always use the ClamAVGUI provided freshclam config file due It is needed to have a correct configurated config file to allow database download at start time if none exist. This is to make it directly usable.

About new save freshclam_GUI.conf , this one should be updated only if ClamAV database path has changed... I'll check what happens here and come back....       

CDRWSel

#5
Hi Dave,

I found the problem and it permited me to find an other minor problem
Could you please get again the updated file and give it a try ?

Latest updates just added
   * Corrected miss-placed instruction making default ClamAV-GUI Freshclam create unwanted backup config file at ClamAV-GUI start time
   * Corrected a possible database update end of process bug
   * Changed how initial ClamAV-GUI start generates default Freshclam config file
   * Corrected a possible not forced ClamD (if running) database reload after database update updated files
   * Corrected ClamD database reload message issued while it should not when no files database updated following a previous freshclam update.

This following first added corrections:
   * Changed RUN= added position into config.sys (to prevent some MPTSTART error at start time if placed as first RUN= statement)
   * Changed REM text when adding Clamd into config.sys
   * Changed process to select ClamD config file. If original Clamd.conf file exist, it is given possibility to use it instead of ClanAV-GUI configured conf file.
   * If original Clamd config file is selected to be used, "epm" opens it to allow user to correct/update his config file (User has to know which parms to add to have clamdscan working)

Thanks and kind regards,
Remy

PS: One more option added
   * ClamD can be auto started from config.sys or startup folder. Entries are created when starting clamd from ClamAV-GUI
      note: When using "startup" folder option, *REM* entries are added into config.sys to inform
ClamAV-GUI

CDRWSel

#6
Hi Dave,

I updated the V2.1.2 test build which seems be very good for me an from other returned feedback but none under RPM/YUM.

Under an other forum thread (in discution with Doug), it was expose the problem to start multiple instance when dropping multiple files on the ClamAV-GUI icon due to same used logfile despite this one has a name using time in seconds in it.
Now I resolved it and you can drag/drop one or multiple files on ClamAV-GUI icon for ponctual scan (up to 1000)

You can get the refreshed v2.1.2 from here
http ://remydodin.levillage.org/outils/ ClamAVGUI-2_1_2.wpi

Please remove blanks into the linkname.

David McKenna

Hi Remy,

  I tried this test version 2.1.2 and I still see the following issue:

Start ClamAVGUI, go to 'Settings' -> 'Clamdscan(conf)' and /etc/clamd.conf opens. Go to 'Settings' -> 'Freshclam(conf)' and /etc/freshclam.conf opens. This is correct for my setup.

Now go to 'Settings' -> 'ClamAV GUI' and hit 'Save' (you can make a change or not). Go back to either 'Clamdscan(conf)' or 'Freshclam(conf)' and now it opens C:\Programs\ClamAVGUI\xxx.conf. This is not correct.

  Also I still get a new freshclam.conf file and copied backup the first time I hit save in ClamAV GUI settings.

  I tried the drag and drop and it seemed to work well... very nice!

Regards,

Dave McKenna

CDRWSel

#8
Quote from: David McKenna on 2011.03.01, 00:23:12

Start ClamAVGUI, go to 'Settings' -> 'Clamdscan(conf)' and /etc/clamd.conf opens. Go to 'Settings' -> 'Freshclam(conf)' and /etc/freshclam.conf opens. This is correct for my setup.

Now go to 'Settings' -> 'ClamAV GUI' and hit 'Save' (you can make a change or not). Go back to either 'Clamdscan(conf)' or 'Freshclam(conf)' and now it opens C:\Programs\ClamAVGUI\xxx.conf. This is not correct.

 Also I still get a new freshclam.conf file and copied backup the first time I hit save in ClamAV GUI settings.


Hi dave,

I'm no more able to get the error about clamd.conf since I did changes.
I could get the freshclam.conf issue you described
This is because you use the clamav provided conf files instead of the clamav-GUI customized freshclam config files which has several backup links configurated in case some update links didn't respond

I didn't change this part of the code and will check this too.

I suppose you choiced to use clamd.conf and not clamd_GUI.conf ?
This selection always forces use of the this config file.... Or did a change I made under the save button dropped ! (I got this kind of problem a few build before and I'll check this and review the code about freshclam)     

Well, could you please send me your clamavgi.ini file under boot_drive: \os2 or under clamavgui path if you moved it there.

Use my clamav-gui "write to the author" email address.
Thanks

Kind regards,
Remy
 
 

CDRWSel

 :o

My supposition was right!  I redo the dropped code from last save
and I added code to set the freshclam config file to use.

Could you please get the v2.1.2 again ?
I refreshed it

Thanks
Kind regards
Remy

David McKenna

Hi Remy,

  I tried the latest (2.1.2) ClamAVGUI and I still see this issue:

Quote from: David McKenna on 2011.03.01, 00:23:12

Start ClamAVGUI, go to 'Settings' -> 'Clamdscan(conf)' and /etc/clamd.conf opens. Go to 'Settings' -> 'Freshclam(conf)' and /etc/freshclam.conf opens. This is correct for my setup.

Now go to 'Settings' -> 'ClamAV GUI' and hit 'Save' (you can make a change or not). Go back to either 'Clamdscan(conf)' or 'Freshclam(conf)' and now it opens C:\Programs\ClamAVGUI\xxx.conf. This is not correct.

  Also I still get a new freshclam.conf file and copied backup the first time I hit save in ClamAV GUI settings.



other than that everything seems to work well.

Regards,

Dave McKenna

CDRWSel

#11
Hi Dave,

I hope you click at least one time on the ClamAV-GUI save button ! (This is a must)  

Wrong opened config file is no more possible due as soon you responded to the message asking you to choice the correct config file at first clamav-gui run time, the path is forced all the time to use this user selected config file with the right name which of course is different. Other existing config files are all ignored...  

About freshclam backup file, this is no more possible too.
You'll have one config file for clamd and fresclam under ClamAV-GUI path and only if you change the database path, a backup is created (there was a bug into previous build but this was corrected and only this condition will create a backup). You must have pressed at lease one time on save to save the presented configuration despite it is correct at first run time to confirm it and save it for reference.  

I would suggest you to erase existing "clamavgi.ini" file et restart ClamAV-GUI. May be something got wrong with it which could explain some issue you have.
By default, clamavgi.ini is under ..:\OS2 path except if you moved it under ClamAV-GUI path. Removing ClamAV-GUI doesn't erase the ini file which is take by any new installation.     

I was waiting on your INI files several days to check it but didn't get it into my mailbox.
May be you can send it to me before you erase it. Thanks

Do you have 2.1.2e ?

Cheers
Remy

David McKenna

Hi Remy,

  I sent the ClamAVGUI.ini file today - I hope you got it.

  I am using version 2.1.2e.

  I tried deleting ClamAVGUI.ini and restarted ClamAVGUI, then went to Settings -> ClamAV GUI and set up everything and saved, but still have the same issues I reported.

  Then, I deleted ClamAVGUI using WarpIn and deleted the remaining ClamAVGUI folders and Clamd object in my startup folder and re-installed ClamAVGUI. During install I was warned that 2 freshclam.conf files exist and to choose 'Yes' if I want to use the ClamAVGUI one. I chose 'No' in order to use the ClamAV one. Same with clamd.conf. Then I was asked about adding clamav.dll to a path and I chose to leave as-is.

  Next, I started ClamAVGUI and went File -> Start Clam Daemon. I was asked how I want to start clamd and I chose put object in startup folder. An object was put into the startup folder called 'Clamd using ClamAVGUI-config'. An error appeared in the ClamAVGUI console saying 'Clam daemon failed (used parms --config-file=C:/etc/clamd.conf RPM installed =0). Looking at the 'Path and File Name' settings of the object in the startup folder, I see it is set to: C:\BIN\CLAMD.EXE. It should be C:\USR\SBIN\CLAMD.EXE. The 'Working Directory' is wrong too.I change them to C:\USR\BIN, then restart Clamd.

  Now I go to 'Settings -> ClamAV GUI'. I click the 'RPM' check box. The paths to ClamAVScan and ClamAV Updater are both set to C:\BIN\xxx.exe. They should be C:\USR\BIN\xxx.exe I change them and the indicators turn green. I hit 'Save' and a message warns that the ClamAV DB path is not correct ( \var\lib\clamav even though the indicator is green) and it changes to C:\var\lib\clamav. I hit 'OK" and then 'Save'.

  Choose Settings -> Clamdscan (conf) and the file C:\Programs\ClamAVGUI\clamd.conf opens. Choose Settings -> Freshclam (conf) and the file C:\Programs\ClamAVGUI\freshclam.conf opens. Now close ClamAVGUI and restart, choose Settings -> Clamdscan (conf) and the file C:\etc\clamd.conf opens. Go to Settings -> ClamAV GUI and hit 'Save'. A new Freshclam.conf is written. Go to Settings -> Clamdscan (conf) and the file C:\Programs\ClamAVGUI.conf opens. Clamd is using C:\etc\clamd.conf as far as I can tell. It seems as long as I do not hit 'Save' in ClamAV GUI settings, the correct *.conf files are displayed.

HTH,

Dave McKenna

CDRWSel

#13
Hi Dave,

RPM/YUM checkbox has to be checked first due you are in a RPM/YUM clamav installed environment.
I'm not able to test this and thanks to you for your effort.

As you wrote: RPM installed = 0  ( this is wrong for you and is an User error  ;D  but not all... )
Never try to start daemon or install it into startup folder while full configuration isn't done.

With RPM/YUM not checked and ClamAV 0.96.4.x was installed as WPI package using previous compatibility, unixroot is added and this one may contain a path
ex: unixroot=C:\programs\clamav
Previous WPI ClamAV as well as the latest WPI have all exe files (including clamd.exe) under \bin (no sbin exist)
So, having unixroot\bin for the daemon is correct and the result you have without RPM/YUM checked is as expected

As you know, RPM/YUM doesn't respect older installation rules and this is why you have to set it first.
With RPM/YUM checked and correct clamdscan.exe or clamscan.exe path selected, the clamd.exe will be search under sbin (RPM is on !) and other exe files under the path where clamdscan anf clamscan are


Once RPM/YUM is set, update parameters at next start and save them. You can then start clamdaemon and add it into startup folder if needed. All parameters when using RPM/YUM are correctly set after full configuration + RP/YUM checkobox is set + restart.

I'm going to send you an update soon which I hope resolves a few issue you have.

Cheers
Remy

Ps: hum ! If you check RPM/YUM, I have to disable saved path for clamd.conf and freshclam.conf...
       I'll do this and send you the update. 
 

CDRWSel