is it possible to log only infected files with ecls?

Discussion in 'ESET NOD32 Antivirus' started by asili, Dec 2, 2007.

Thread Status:
Not open for further replies.
  1. asili

    asili Registered Member

    Joined:
    Dec 2, 2007
    Posts:
    5
    I am using the ecls.exe process to do the scanning but even with the
    /no-log-all parameter i'm still getting the clean files either.

    is there an option getting only the infected files?

    thanx
     
  2. nodyforever

    nodyforever Registered Member

    Joined:
    Oct 30, 2007
    Posts:
    549
    Location:
    PT / Lisbon

    See:

    "C:\Program Files\ESET\ESET NOD32 Antivirus\ecls.exe" /base-dir="C:\Program Files\ESET\ESET NOD32 Antivirus" /auto /files /boots /arch /mail /sfx /rtp /subdir /max-subdir-level=0 /symlink /adware /unsafe /unwanted /pattern /heur /adv-heur /action=clean /quarantine /aind /log-all




    More information:


    "C:\Program Files\ESET\ESET NOD32 Antivirus\ecls.exe" /help


    or


    Help and Support - Open Help - Tools - Command Line




    Best Regards :)
     
  3. asili

    asili Registered Member

    Joined:
    Dec 2, 2007
    Posts:
    5
    thanx for your answer but i want to log only the infected files.
    /log-all logs all of the scanned files and thats not what i am looking for.

    btw is there an option updating the virus signatures by command line?
    thanx
     
  4. nodyforever

    nodyforever Registered Member

    Joined:
    Oct 30, 2007
    Posts:
    549
    Location:
    PT / Lisbon
    Four options:

    Logs:
    --log-file=FILE log output to FILE
    --log-rewrite overwrite output file (default - append)
    --log-all also log clean files
    --no-log-all do not log clean files (default)


    ----------


    No updating the virus signature by command line. Command line use database signatures updating EAV or ESS



    Best Regards
     
  5. ASpace

    ASpace Guest

    asili , that is a known bug with the ECLS logging which is already fixed in the new release ( I got confirmation from ESET Support) . We can only hope it becomes available sooner :thumb:
     
  6. BradenD

    BradenD Registered Member

    Joined:
    Dec 3, 2007
    Posts:
    6
    For now, you can easily circumvent the logging bug with the following command:

    find /i /v "is OK" log.txt|find /i /v "error opening" > parsedlog.txt

    Replace log.txt with the name of your log, of course.
    This method actually kind of has advantages, as then you have both logs!
     
Thread Status:
Not open for further replies.