Hello,


I have a weird problem.
Rsync works fine if it is ran by me manually; i restrict the upload rate, and the bandwidth doesnt suffer, users and rsync may work at the same time.

But when i set crond to schedule rsync, it doesnt matter if i set the limit rate, if i use "trickle" to limit the upload or whatever, rsync uses the 100% of available bandwidth, making imposible to use the network.

In crond, i exaclty wrote the same command line i use manually which work, and i did program it every 30 minutes, so backups doesnt start before the previous finished.

I dont know what happends... ideas?

Is it running in the essence by the same user and the same nice value?

same user yes
about the nice value, i dont know what it is...

The default is a value of zero for user processes. It should be the same for the processes running by a cron entry, unless you specify it explicitly.

But you can of course try to lower its priority to test it. You have to prefix the command in your cron entry by which should be a shortcut to and results in a priority of plus 19, i.e. the lowest possible one on Linux (on BSD it would be 20).

mmm i dont know, i smell something bad in rsync.

Look, i tryed to synch a 2 gb file over a LAN manually, no cron.

I set --progress --bwlimit=15 because it was set in my script from the last file i put over the internet.

Guess what?
the average uploading rate was: 15MB/sec

The man page says:
--bwlimit=<rate>Kb

So i dont know what is the problem.

Is your version accepting an unit for --bwlimit?

https://bugzilla.samba.org/show_bug.cgi?id=6881

yes it does

to sum up:


--bwlimit=15


LAN -> 15MB/s

WAN -> 15 KB/s

WAN & cron: -> doesnt work