> The directories exist as specified. There is also cron.daily and cron.d > (what does the latter do?)
cron.d is used internally by the cron program - it's used to store cron files in, but you don't need to worry about that. > How do I plonk the script from #1 in that directory, and what is plonking? That's Maltese for "put the script in that directory" :) > I must be srewing something up because it doesn't seem that simple. Basically, any executable program or script that you place in cron.weekly will run every week, those in cron.daily will run every day, etc. So if you copy the perl script into the cron.weekly directory you should get the updates every week. > The above explanation I understood well. I have a question, do I have to > change the directory to the cron.weekly directory in the console if I want > to create a weekly operation? No. If you use the first option, eg. the cron.weekly directory, you just have to copy the perl file into that directory, OR create a shell script in that directory which invokes the perl script from its original directory. The latter may be a good idea so if you get a new version of F-Prot, the perl script will be updated too. If you use the second option, ie: use the "crontab -e" command, you must specify the full directory name for the perl script. > Also, when I ran crontab -e (in the console as root) all I got was a screen > with ~ on all lines except the few at the bottom of the screen where I got > some details. You're in the "vi" editor, which may take some getting used to if you've never used it before. Type "export EDITOR=kedit" before typing the "crontab -e" command. That tells crontab that you want to use kedit as your editor. That should be more familiar. You can replace kedit with the name of any other editor. ________________________________________________________________________ Ramon Casha Malta Linux User Group (http://linux.org.mt)
