• 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.0.0

Started by CDRWSel, 2011.02.09, 09:56:57

Previous topic - Next topic

jep

Quote from: CDRWSel on 2011.02.15, 01:12:31
I'm surprised about the accounts path !
I installed the WPI and it adds the acounts under C:\programs\PMMail\ACCOUNTS

Don't be surprised, because I don't use the default accounts path, I've placed mine on a server several years ago so that I can access my email from any of my computers.

I'll fetch and try the new version as time permit.

The problem with clamscan failing with memory problem still remain now that I've set it to recurse only 5 levels.
I tried even lower both levels and it succeded to scan C: with both options set to 1.  :-\
I also set some files in the exclude list and turend that option on, but no difference is notable.
Anyway the memory problem doesn't seem to appear at the exactly same spot every time... if that is a clue.

Thank you for uor help
//Jan-Erik


CDRWSel

#16
Hi Jep,

I found an error in my code !
I corrected it now and this affected clamscan process but not the "clamscan memory issue"
(please get the refeshed package and you should have v2.1.0k under about)

Of course, you can do a try using Clamdscan to check result (with and without "verbose")
note: You should have at least "clamscan_201" and "clamdscan_201" in the exclude list

Cheers
Remy

note: I could get the same memory issue now. I'll check if older clamscan version have the same problem or not !

CDRWSel

#17
Changing clamscan version doesn't resolve this...
I could read on ClamAV reported bugs that they are working on a new process to unload memory !
I think that the best would be to contact Yuri which ported clamav to os/2 (eCS)
I did a test adding a debug option into clamscan but it writes not been supported...  

About clamd
Killed by SIGSEGV
pid=0x0246 ppid=0x0245 tid=0x0003 slot=0x00a9 pri=0x0200 mc=0x0001
E:\CLAMAV0964\BIN\CLAMD.EXE
CLAMAV 0:000d9315
cs:eip=005b:13709315      ss:esp=0053:026af688      ebp=026af6b4
ds=0053      es=0053      fs=150b      gs=0000     efl=00010206
eax=ffffffff ebx=98badcfe ecx=efcdab89 edx=67452301 edi=ffffffff esi=10325476
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

I would suggest prevent specify full path and created lists with sensible path to test
Enable than "scan root+os" option    

I would be interested by Dave results which has ClamAV RPM/YUM installed.

and here the clamscan error when run out of GUI (command line)
...
C:\programs/python26/lib/stringprep.py: Can't allocate memory ERROR
scanning C:\programs/python26/lib/struct.py
LibClamAV Error: cli_malloc(): Can't allocate memory (131564 bytes).
malloc_problem: Not enough memory
C:\programs/python26/lib/struct.py: Can't allocate memory ERROR
Scanning C:\programs/python26/lib/struct.pyc
LibClamAV Error: cli_calloc(): Can't allocate memory (1792 bytes).
calloc_problem: Not enough memory
LibClamAV Error: cli_ac_init: Can't allocate memory for data->lsigsuboff[0]
C:\programs/python26/lib/struct.pyc: OK
Scanning C:\programs/python26/lib/subprocess.py

Killed by SIGSEGV
pid=0x00ad ppid=0x00ac tid=0x0001 slot=0x0086 pri=0x0200 mc=0x0001
C:\PROGRAMS\CLAMAV\BIN\CLAMSCAN.EXE
CLAMAV 0:000d9315
cs:eip=005b:1fdd9315      ss:esp=0053:0013d26c      ebp=0013d298
ds=0053      es=0053      fs=150b      gs=0000     efl=00010206
eax=ffffffff ebx=98badcfe ecx=efcdab89 edx=67452301 edi=ffffffff esi=10325476
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

CDRWSel

ClamAV-GUI V2.1.0 refreshed
(may be it is final V2.1.0 before release)   

jep

Hello,

Quote from: CDRWSel on 2011.02.15, 13:49:07
Changing clamscan version doesn't resolve this...
I could read on ClamAV reported bugs that they are working on a new process to unload memory !
I think that the best would be to contact Yuri which ported clamav to os/2 (eCS)
I did a test adding a debug option into clamscan but it writes not been supported...

Do you contact Yuri about the clamscan memory problem that know what you're talking about?!

Thanks
//Jan-Erik

CDRWSel

#20
I would suggest those having RPM/YUM installed to try getting feedback from him  ::)
I don't have it (not ok) and great thanks to Dave having tested the GUI for full compatibility with ClamAV using this process.  

For me, it looks like this was a known problem to ClamAV and found several post about changes into the code to use "NULL" in case of memory issue  (May it be possible he didn't correct the NULL syntax for Os/2 ? I don't know)

PS: Do you have ClamDscan errors into POPUPLOG.OS2 too ??

Remy

jep

Quote from: CDRWSel on 2011.02.18, 09:48:38
I would suggest those having RPM/YUM installed to try getting feedback from him  ::)
I don't have it (not ok) and great thanks to Dave having tested the GUI for full compatibility with ClamAV using this process.  

For me, it looks like this was a known problem to ClamAV and found several post about changes into the code to use "NULL" in case of memory issue  (May it be possible he didn't correct the NULL syntax for Os/2 ? I don't know)

I'll let Dave and Yuri sort that out on their own instead. :-X

Quote from: CDRWSel on 2011.02.18, 09:48:38
PS: Do you have ClamDscan errors into POPUPLOG.OS2 too ??

Remy
I have repeated entries in Popuplog.os2 that resemble this one
==========
02-14-2011  20:13:22  SYS2070  PID 01b6  TID 0001  Slot 00f5
C:\PROGRAMS\CLAMAV\BIN\CLAMDSCAN.EXE
CLAMDSCAN->MMAP._mcommit
127
------------------------------------------------------------

CDRWSel

#22
Yes, same entries here

Look here =>  http://svn.netlabs.org/ports/timeline?from=2011-01-09&daysback=30  


note: "Clamav.dll and Clamd*" from latest RPM/YUM are not working despite all DLL's are installed (internal error). This is why clamav.dll and clamd* are from 0.96.4.1 in the WPI

David McKenna

Hi Remy,

  I haven't had any trouble with running clamscan or clamdscan (I usually use clamscan). I can manually start clamd from the GUI, but I have had trouble booting with Run=clamd.exe in my config.sys. The trouble is that boot hangs on MPTSTART when it is present, so I'm not sure yet what the problem is (may be configuration). I'm new to ClamAV so I need to learn.

  I also use PMMail, but I have not been able to get 'write to GUI author' to work - ClamAVGUI crashes and I get this error when I try:

02-19-2011  17:34:35  SYS3175  PID 0084  TID 0001  Slot 00c8
C:\PROGRAMS\CLAMAVGUI\CLAMAVGUI.EXE
c0000005
00014cb7
P1=00000001  P2=fffffffc  P3=XXXXXXXX  P4=XXXXXXXX 
EAX=00045fb8  EBX=000460e4  ECX=00010084  EDX=00000000
ESI=8000010a  EDI=80000001 
DS=0053  DSACC=f0f3  DSLIM=ffffffff 
ES=0053  ESACC=f0f3  ESLIM=ffffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:00014cb7  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:00045f88  SSACC=f0f3  SSLIM=ffffffff
EBP=00045fc0  FLG=00010246

CLAMAVGUI.EXE 0001:00004cb7

Thanks again for providing ClamAVGUI.

Regards,

Dave McKenna

CDRWSel

#24
Hi Dave,

For Clamd started from config.sys, could you do a try moving the line as last config.sys entry ?
Of course, Yuri is the right contact for ClamAV issue

If starting Clamd from config.sys creates problem, I can review code to start it from startup.cmd
May you could give it a try
a/ If your startup.cmd is a rexx: add the string after RUN= into startup.cmd prefixed by START /MIN and the whole string into quotes e.g. 'START /MIN C:\usr\sbin\clamd.exe ..................    '
b/ If it isn't a rexx, add the same except quotes
Ed the file with an exit   

About the second reported problem, which version do you use (please check under about)
I've put during last night the release online but I had to replace it due a wrong build was picked up during the script process. It is ok now under my site (I apology)

David McKenna

Remy,

  OK, when I get some time I will try moving the Clamd.exe line in Config.sys to the end.

  I just downloaded the latest ClamAVGUI (2.1.0s) and I still have the issue with 'write to GUI Author'. When I try, the program crashes and a little window very briefly appears (some kind of runtime console?). It also disappears quickly, but I could see that there are two lines in it and they start with:

546 ++ Def_mailparms = '-cwd" ' || substr(......

Rexx 0036  Error 36 running C:\Programs\CLAMAVGUI\CLAMAVGUI.EXE Line........

That's all I could make out.

Regards,

Dave McKenna

CDRWSel

#26
Hi Dave,

I did my test using latest PMMail program.
The program path should have a \bin in its name. Right ?
It looks like something isn't set as expected under your environement.

I just added a check about the path but something may be wrong under you os2 ini setting for pmmail.
I would like know what you have into your os2 ini file about default mail program and Pmmail ?
(of course, you can get the file again from my web link)

e.g.
PMMail/2      InstallRoot     c:\programs\PMMAil\bin

And
WPURLDEFAULTSETTINGS    DefaultMailExe    c:\programs\PMMail\bin\pmmail.exe
                                                         DefaultMailParameters   ........
                                                         DefaulMailWorkingDir    c:\programs\PMMail\bin

Thanks
Remy

DougB

Actually, those settings, for PMMail, would not be correct, for a default PMMail 3.x installation. The DefaultMailWorkingDir would be: "c:\programs\PMMail\Accounts".

t would be better to do as I do, and have PMMail call clamdscan to scan each message, as it arrives. What I use, is a REXX cmd file:
ClamDScanPMM.CMD
==============================
/* Clamscan for PMMail */

/* Load REXXUTIL.DLL */
call RxFuncAdd 'SysLoadFuncs', 'RexxUtil', 'SysLoadFuncs'
call SysLoadFuncs

x = setlocal();

fname=arg(1)

fname=strip(fname)
/* if pos(' ',strip(fname))>0 then fname='"'fname'"' */

Curdir=directory()
CSdir=directory("\APPS\ClamAV\bin")

rc=lineOut('../Logs/ClanDscanPMM.log','===============================')
rc=lineOut('../Logs/ClanDscanPMM.log',Date()' 'Time())
rc=stream('../Logs/ClanDscanPMM.log','C','CLOSE')

'SET UNIXROOT=W:\APPS\CLAMAV'
'ClamDscan.exe --config-file=../etc/clamd.conf -l ../Logs/ClanDscanPMM.log' fname

RetCode=rc

if RetCode=1 then do
  do while lines(fname)
    Newline=lineIn(fname)
    if left(Newline,8)="Subject:" then do
      Newline=insert(' [SUSPECTED VIRUS]',Newline,8,18)
    end
    rc=lineOut(fname'.out',Newline)
  end
  rc=lineOut(fname'.out')
  rc=stream(fname,'C','CLOSE')
  rc=sysFileDelete(fname)
  'copy 'fname'.out 'fname
  rc=sysFileDelete(fname'.out')
end
if RetCode>1 then do
  rc=lineOut('../Logs/ClanDscanPMM.log','SCANNER FAILED RC='RetCode)
  rc=stream('../Logs/ClanDscanPMM.log','C','CLOSE')
end
olddir=directory(Curdir)

x = endlocal();

exit
===================
and then add that as a REXX exit to run as each file is received. I then filter on the phrase "[SUSPECTED VIRUS]" to put the suspected virus into a special folder, for further investigation. It could just move it somewhere else, or simply delete it, depending on how you wish to handle the file.

Note that I use:
'SET UNIXROOT=W:\APPS\CLAMAV'
to replace the default UNIXROOT, which is used for SAMBA (x:\MPTN\ETC), and isn't the same as what I want to use for ClamAV (or anything else). In fact, it would be far better to use RUN! to set the Environment up properly for ClamAV (and other things). This nonsense was not needed before the latest update produced by Yuri for RPM/YUM.

Mentioning that, it is NOT good for your installer to mess with what is in the UNIXROOT entry in CONFIG.SYS. It is probably also not good to use that entry for ClamAV(GUI). You will probably break something else (like SAMBA).

CDRWSel

ClamAV-GUI doesn't need unixroot an I may suggest you give it a try :-D
It is checking for it when ClamAV was installed through RPM/YUM which requires UNIXROOT being set into config.sys and when using latest ClamAV 0.96.4.x (@UNIXROOT should be set at root level). This is main RPM/YUM requirement

About PMMail install path, it is like I wrote due I installed latest PMMail WPI package and I checked all ini setting after a well installation.
PMMail is installed under  boot_drive\...\PMMail\bin
the account are under boot_drive\...\PMMail\Account
This is conform to what Jep wrote too.

The reported question was not about how to scan PMMail message but about how to write to me using the
clamav-gui "write to author" option with PMMail. 

kind regards
Remy

David McKenna

Hi Remy,

  Here are my settings:

PMMail/2  Install Root C:\programs\PMMail\bin

WPURLDEFAULTSETTINGS:  DefaultMailExe  C:\programs\PMMail\bin\PMMail.exe
                                     DefaultMailParameters  -compose
                                     DefaultMailWorkingDir   C:\programs\PMMail\Accounts

This is how it was installed by PMMail on my machine.

HTH,

Dave McKenna