On Thu, 14 Apr 2005 16:55:29 +0200 Paul <[EMAIL PROTECTED]> wrote: > Op Fri, 15 Apr 2005 02:21:16 +1200 schreef Rosemary McGillicuddy: > > >> If you need help with this, just show us what you got so far. > >> > >> Paul > > >For some reason every time I try to copy and paste from konsole I > >get a clamav url, so makes things longwinded! > > > >I tried 'check-updates.pl' after 'cd'ing to file and doing su. Got > >'command not found'. These instructions from > >www.f-prot.com/support/unix/unix_manpages/check-updates.pl > > > >Probably something basic I am doing or not doing ... > > Okay, for the updater the info on the web is rather straightforward: > > "To run this script as a cron-job, it is necessary to create a crontab > entry similar to the following example. Here is an example of a > crontab entry which runs the check-updates.pl script twice a day: > 04:27 and 16:27:" > > 27 4,16 * * * /usr/local/f-prot/tools/check-updates.pl -cron > > First make sure that you know where 'check-updates.pl' is installed. > Is that in /usr/local/f-prot/tools? If not, remember the directory > where it is. > > su to become root. > Then type "crontab -e" (without the quotes) > > You'll probably be prompted with the vi-editor. > Type 'i' to go to insert mode > Then type > > 27 4,16 * * * /<directory_where_it_is>/check-updates.pl -cron > > where <directory_where_it_is> of course is the path to the directory > where check-updates.pl is located on your system. > The 27 means 27 minutes past, the 4,16 means 4 o'clock and 16 o'clock > (4pm). That means the script will check twice a day for updates, at > 4:27am and 4:27pm. You can change that to your liking, any minute > lower than 60 will do, and you can also just let it check once a day. > The * * * means every day. > > When you set this up, press ESCape and type: > > :wq > > in vi. That saves the cron-file and from that moment on the check runs > at the time you set it up. > > A similar thing goes for f-prot. It is probably located in the same > directory (if not, look where f-prot is and remember that/write it > down). > > First now, you decide how you want to be told by f-prot what it did. > The default way of reporting from f-prot is to dump its text to the > screen. When it runs from cron, you won't see that. > You can tell it to write to a report file: > > f-prot -report=$HOME/Rosemary/temp/f-protreport.txt would write a > report in$HOME/Rosemary/temp/f-protreport.txt (make sure that > $HOME/Rosemary/temp/ exists, of course). > This would however overwrite the old report. So you can do > > f-prot -report=$HOME/Rosemary/temp/f-protreport.txt -append > > More options are visible at > http://www.f-prot.com/support/unix/unix_manpages/f-prot.1.html, but > the default is a good start for now, I think. > > To add that to cron, you can do this in the same manner (at the same > time) that you update cron for the update.pl script. > > su to root > crontab -e > i for insert mode > > Then tell cron when it should check. Once a day? Every hour? This is > up to you. > > Once a day, at 8:15 am would look like this: > > 15 8 * * * /path_to_program/f-prot > -report=$HOME/Rosemary/temp/f-protreport.txt -append -silent > > Twice a day at 8:15am and 8:15 pm is > > 15 8,20 * * * /path_to_program/f-prot > -report=$HOME/Rosemary/temp/f-protreport.txt -append -silent > Every hour at 20 minutes past the hour is > > 20 * * * * /path_to_program/f-prot > -report=$HOME/Rosemary/temp/f-protreport.txt -append -silent > > > The -silent option is recommended on the f-prot page when running from > cron. > > Then ESCape again, and :wq to end vi and start the new cron jobs. > > I'd advise you to first try out the commands (without the 20 * * * > stuff of course) from the CLI (command line interface) to make sure > they work. Otherwise you get nothing from cron and you don't know why. > > Good practice also, in your cron setup, is to write something like > this at the top: > > SHELL=/bin/sh > [EMAIL PROTECTED] > > (Use an e-mail address that you can use on your machine.) That will > make cron send you an e-mail when something happened through cron. > Very useful when something goes wrong. > > > Good luck and let's hear what works and what doesn't. > > Paul > > -- > Let he who takes the plunge remember to return it by Tuesday. > > http://www.nlpagan.net/linux.php > Have you visited http://twiki.mdklinuxfaq.org yet? >
Thank you Paul. I need to have a good read before I attempt this. Some of it looks familiar, so not all entirely mindboggling. I appreciate such detailed instructions - by doing I think I can learn. Thanks again Rosemary -- Registered linux user # 386597 A friend may well be a masterpiece of nature. Emerson
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
