-
 KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
--
-
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
--
-
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
--
-
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
--
-
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
--
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    LinuxDaily.com    Linux42.org    OpenSkillz.com   
 
Apps
News
Groups
Knowledge
Events
Forum
People
Jobs
Register
Login


Sponsoring


-
- Content .- Fans (7) .- Knowledge Base  . 

Scan with ClamAV (extended)

   2.5.7  

KDE Service Menu

Score 74%
Scan with ClamAV (extended)
zoom


Scan with ClamAV (extended)
zoom


Scan with ClamAV (extended)
zoom


Minimum required   KDE 4.x
Downloads:  2764
Submitted:  Jan 8 2011
Updated:  Jun 18 2013

Description:

A short script to scan files or directories with ClamAV.
It provides the ability to scan multiple files, a progress-dialog and a result window.

Installation:
1. Start Dollphin
2. Press "Configure and control Dolphin" > "Configure Dolphin..."
3. Go to "Services"
4. "Download New Services..."
5. Search for my scripts name
6. Press "Install"

You need to have ClamAV installed.
If you encounter any issues when using the graphical way extract the file and run "sh install.sh".

All files are installed in the users home directory (/home/[user]/.kde[4]/share/kde4/services/ServiceMenus/ClamScan/), there is no need to use su or sudo to install

Note:
The script is currently translated in English, Finnish, French, German, Indonesian, Italian, Russian, Spanish, Swedish, Turkish and Ukrainian.
If you wish another language, translate the following and leave me a message or write it in a comment:
Name[en]=Scan with ClamAV
wait="ClamAV is scanning, please wait."
not_found="ClamAV is not installed!"
scan_sentence="Scanning files: "

Translations:
  • English
  • Finnish (Thanks to nikore90)
  • French (Thanks to pbuard)
  • German
  • Indonesian (Thanks to JamurBulet)
  • Italian (Thanks to Andrea Sciucca)
  • Russian (Thanks to Omega9)
  • Spanish
  • Swedish (Thanks to Jonas Norlander)
  • Turkish (Thanks to tanzer)
  • Ukrainian (Thanks to Localizator (localizator@ukr.net))



  • Changelog:

    2013-6-18 (2.5.7)
    - fixed permissions

    2012-9-16 (2.5.6)
    - fix: install-script: create path2 if it doesn't exist

    2012-4-21 (2.5.5)
    - support for linked directories
    - support for empty directories
    - unnecessary logfile gets deleted after scan, only result file remains
    - fixed some if-conditions
    - counts directories

    2012-4-19 (2.5.4)
    - fixed a wrong directory test (minor bug); now [ -d ] instead of [ -f ]
    - did some testing on the mountable devices .desktop file, seems to work fine now

    2012-4-19 (2.5.3)
    - fixed a wrong set directory (~/.kde4/...) (that was for testing, I forgot to remove it)
    - added spanish
    - fixed this bug: gentooforum.de/artikel/17867/2/update-script.html when running ClamScan.sh without syntax

    2012-2-23 (2.5.2)
    - fixed recognition of empty directories which I broke in 2.3

    2012-2-23 (2.5.1)
    - Indonesian translation

    2012-2-4 (2.5)
    - using mkdir -p instead of if-conditions

    (See Changelog file)

    Don't forget to vote!




    LicenseCreative Commons by
    (137158-ClamScan.tar.gz)
    Send to a friend
    Subscribe
    Other  Apps  from Incarus
    Report inappropriate content



    goto page: prev   1  2  3  4 

    -
    .

     Voted and Fan-ed

     
     by msx on: Jul 26 2013
     
    Score 63%

    Do I miss something!? xD


    Reply to this

    -
    .

     ClamScan shell script update needed

     
     by webguy on: Dec 1 2013
     
    Score 63%

    A small thing, but the ClamScan.sh file still includes the line 'version=2.5.5', which is confusing for version 2.5.7, as the KDialog box title bar includes the version number
    It also doesn't display the full result of the scan, just 'Result' with a dotted line underneath. The log for the day, and the individual scan logs have the full details though.


    Reply to this

    -

     Re: ClamScan shell script update needed

     
     by Incarus on: Dec 2 2013
     
    Score 50%

    Thanks for your Feedback. I hope that I can fix this bugs in the next days but I can not longer maintain the script due to a couple of reasons.

    Feel free to fork this project and to maintain your own script, I also changed the license to CC BY (now without SA).


    Reply to this

    -

     Progress Bar

     
     by mcmurchy1917 on: Dec 5 2013
     
    Score 63%

    Firstly can I say this is a great tool and note that Incarus has "retired" as maintainer.

    However, I've noticed that the progress bar in kdialog doesn't behave correctly.

    I believe this patch resolves the issue -

    --- ClamScan.sh.clamscan 2013-12-04 16:28:42.137603031 +0000
    +++ ClamScan.sh 2013-12-05 10:40:06.303412347 +0000
    @@ -8,7 +8,7 @@
    files_old=$*
    IFS="," #new separator instead of spaces
    files=${files_old//\ \//,\/} #from " /" to ",/"
    -version="2.5.5"
    +version="2.5.8"
    title="ClamScan $version"
    date="$(date +"%H-%M-%S_%d-%m-%Y")"
    path="$(kde4-config --path services)"
    @@ -85,7 +85,7 @@
    current_lines="0"

    progress=$(kdialog --title "$title" --progressbar "$wait
    -$scan_sentence $complete_amount ($complete_amount_dir directories)")
    +$scan_sentence $complete_amount ($complete_amount_dir directories)" $complete_amount)

    #qdbus $progress org.kde.kdialog.ProgressDialog.showCancelButton true
    else


    Reply to this

    -

     Re: Progress Bar

     
     by Xwang1976 on: Apr 22 2014
     
    Score 63%

    I've manually applied the patch and still the progress bar does not update at all.
    Can you help me, please?


    Reply to this

    -

     Re: Re: Progress Bar

     
     by Incarus on: Apr 22 2014
     
    Score 50%

    So let's see what the problem is here. The script actually checks the amount of lines in the file

    "$spath"/ServiceMenus/ClamScan/logs/ClamScan_$date.log

    each scanned file creates exactly one new line in that file, so if the amount of lines in the file == amount of all selected files the progressbar should be 100% (or x of x files).
    Does the mentioned file exist on your computer (is it creating while scanning)?


    Reply to this

    -

     Re: Re: Re: Progress Bar

     
     by Xwang1976 on: Apr 22 2014
     
    Score 50%

    Yes, it is created and the files are added to it (it is automatically removed when I close the popup which contains the scan results).


    Reply to this

    -

     Re: Progress Bar

     
     by mcmurchy1917 on: Jun 3 2014
     
    Score 63%

    I found there was a significant overhead in using clamscan for scanning small numbers of files.

    On my system it takes about 7.318 secs to load the dictionary and scan the smallest file in a directory. Whereas if I scan all 11 files in the directory clamscan takes 7.785 secs so really it takes only 0.467 secs to scan the 11 files.

    How this may be represented in the progress bar is that it displays the bar waits 7.318 secs at 0% then progresses to 100% in the remaining 0.467 secs them closes. Is this what you see?

    I think this was one of the reasons I swapped over to using clamdscan.


    In this scenario the progress bar might not register anything for the first 7 secs and then


    Reply to this

    -

     Re: Re: Progress Bar

     
     by Incarus on: Jun 3 2014
     
    Score 50%

    This is actually a wanted behaviour. The progressbar is set to for example 1300, if you scan 1300 files. A small file will also count as much as a big file for the progressbar. It would be possibly to change that behavior but it would increase the amount of code. For example you could check how big the single files are (in order of the scanned files) and give the single lines a relative count (the script checks the lines of the log file: 1 more line in the log file is +1 for the progressbar until amount of lines = amount of selected files = length of the progressbar.


    Reply to this

    -

     Re: Re: Re: Progress Bar

     
     by Xwang1976 on: Jun 3 2014
     
    Score 50%

    My problem is that I don't see the progress bar at all even if I scan more files.
    Xwang


    Reply to this

    -

     Re: Re: Re: Re: Progress Bar

     
     by Incarus on: Jun 3 2014
     
    Score 50%

    The problem is that I can't fix this right now as I don't have access to a linux machine.


    Reply to this

    -

     Re: Re: Re: Progress Bar

     
     by mcmurchy1917 on: Jun 4 2014
     
    Score 50%

    Incarus

    I understand that this is wanted behaviour and the code should be kept easily maintainable.

    All I was pointing out was that there is an overhead that might suggest the progress bar is not working as designed.

    So waiting for a reply from Xwang1976 to see if what they see can be explained by the above description.

    Alex


    Reply to this

    -

     Re: Re: Re: Re: Progress Bar

     
     by Incarus on: Jun 4 2014
     
    Score 50%

    He could also do some testing out of the box if --progressbar is even working for him: http://techbase.kde.org/Development/Tutorials/Shell_Scripting_with_KDE_Dialogs#Progress_Dialogs

    Might be a problem with DBus.


    Reply to this

    -

     clamdscan

     
     by mcmurchy1917 on: Dec 5 2013
     
    Score 63%

    AS it stands the script ClamScan.sh uses clamscan as the scanner.

    As I have clamd running I've amended the script ClamScan.sh to use clamdscan instead. Needed a bit of rework to cater for the differences in the information they write to the log files and of course clamd must be running.

    The time to scan has reduced quite significantly. I tested on a directory with 1210 files and 9 sub-directories with a size of 3.2G, in the directory there were 19 infected files. My machine is 10 years old with P4 and 2G of memory.

    Using clamscan it took on average 14 mins.

    Clamdscan took on average 2.5 minutes.

    Not quite sure what to do with it. Let me know whoever might be interested. It doesn't cater for symbolic links. So really this is just a heads up.

    Alex


    Reply to this

    -

     Re: clamdscan

     
     by Incarus on: Apr 22 2014
     
    Score 50%

    The thought behind using clamscan instead of clamdscan is that not everybody is running or using clamdscan. Not sure if at the mean time something changed about that, but it was at least not easy back in that time to set up clamdscan, at least clamscan was running out of the box.

    A possible fix for this would be to let the script check if clamdscan is running and if yes to prefer that one.


    Reply to this

    -

     Re: clamdscan

     
     by Incarus on: Apr 22 2014
     
    Score 50%

    the current command to run clamscan in this script is:

    nohup clamscan -r --log="$spath"/ServiceMenus/ClamScan/logs/ClamScan_result_$date.log --stdout $real_files > "$spath"/ServiceMenus/ClamScan/logs/ClamScan_$date.log 2>&1 &

    we could swap it to something like

    if [ "$(pidof clamdscan)" ]
    then
    nohup clamdscan [...]
    else
    nohup clamscan [...]
    fi

    not sure if that is working.


    Reply to this

    goto page: prev   1  2  3  4 

    Add commentBack






    -
    -
    How do you like Plasma 5?
     The best KDE Desktop ever.
     Definitely a nice improvement.
     Not decided yet. Haven't tried it yet.
     I do not like some of the changes.
     KDE is taking the wrong way.
     I am still sticking with KDE 3.5.
     I have no opinion, but wanted to vote anyway.

    resultmore
     
     
     Who we are
    Contact
    More about us
    Frequently Asked Questions
    Register
    Twitter
    Blog
    Explore
    Apps
    Jobs
    Knowledge
    Events
    People
    Updates on identi.ca
    Updates on Twitter
    Facebook App
    Content RSS   
    Events RSS   

    Participate
    Groups
    Forum
    Add App
    Public API
    About KDE-Apps.org
    Legal Notice
    Spreadshirt Shop
    CafePress Shop
    Advertising
    Sponsor us
    Report Abuse
     

    Copyright 2003-2014 KDE-Apps.org Team  
    All rights reserved. KDE-Apps.org is not liable for any content or goods on this site.
    All contributors are responsible for the lawfulness of their uploads.
    KDE and K Desktop Environment are trademarks of KDE e.V.