Usefull especially when transferring data. It's better to transfer data at night, when
others do not need network

One way to solve the problem:
The times when cron launches commands are set in file /etc/crontab
Here's an example of crontab file:
You can make comments in the file, by adding # mark at the beginning of theSHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/
# runparts
01 * * * * root runparts /etc/cron.hourly
02 4 * * * root runparts /etc/cron.daily
22 4 * * 0 root runparts /etc/cron.weekly
42 4 1 * * root runparts /etc/cron.monthly
comment line.
Now, the runtimes are set in lines below the runparts comment
far left is the folder from which the scripts are being executed at the time the line
specifies. Usually as names of those folders do suggest, scripts in cron.hourly folder
are executed once/hour, cron.daily once / day etc.
I think runparts word tells that it is folder, and that all scripts in it should be
executed.
root is most probably the user whose privileges will be used when executing the
scripts.
then there's places for 5 values. (values or asterix)
first is the minute in wich the script will be executed. As you see, cron.hourly has only
the minute specified (* means that all values are ok). It is set to 01, so all scripts in
cron.hourly will be executed at the first minute of an hour. And since there's no other
values specified, it means that regardless of what hour/day/week etc. it is, scripts will
be executed if minute is 01 = every hour.
Next is hour. As you see, cron hourly scripts are to be executed every time hour is 04
and minute 02. That means 04:02 AM every day.
Third is day of month, fourth is month and last one is day of week. Beware day of
week. Sometimes cron is set to start the week from sunday, sometimes from monday.
Well, luckily at least cron with fedora is set to accept not only numeric values, but
also 3 first letters in the name of day. IE. Mon instead of 1...