Archiver not picking up changes to archive_command

Hi,

I'm stumped by an issue we are experiencing at the moment. We have
been successfully archiving logs to two standby sites for many months
now using the following command:

rsync -a %p postgres(at)192(dot)168(dot)80(dot)174:/WAL_Archive/ && rsync
--bwlimit=1250 -az %p postgres(at)14(dot)121(dot)70(dot)98:/WAL_Archive/

Due to some heavy processing today, we have been falling behind on
shipping log files (by about a 1000 logs or so), so wanted to up our
bwlimit like so:

rsync -a %p postgres(at)192(dot)168(dot)80(dot)174:/WAL_Archive/ && rsync
--bwlimit=1875 -az %p postgres(at)14(dot)121(dot)70(dot)98:/WAL_Archive/

The db is showing the change.
SHOW archive_command:
rsync -a %p postgres(at)192(dot)168(dot)80(dot)174:/WAL_Archive/ && rsync
--bwlimit=1875 -az %p postgres(at)14(dot)121(dot)70(dot)98:/WAL_Archive/

Yet, the running processes never get above the original bwlimit of
1250. Have I missed a step? Would "kill -HUP <archiver pid>" help?
(I'm leery of trying that untested though)

ps aux | grep rsync
postgres 27704 0.0 0.0 63820 1068 ? S 16:55 0:00 sh -c
rsync -a pg_xlog/000000010000071700000070
postgres(at)192(dot)168(dot)80(dot)174:/WAL_Archive/ && rsync --bwlimit=1250 -az
pg_xlog/000000010000071700000070 postgres(at)14(dot)121(dot)70(dot)98:/WAL_Archive/
postgres 27714 37.2 0.0 68716 1612 ? S 16:55 0:01 rsync
--bwlimit=1250 -az pg_xlog/000000010000071700000070
postgres(at)14(dot)121(dot)70(dot)98:/WAL_Archive/
postgres 27715 3.0 0.0 60764 5648 ? S 16:55 0:00 ssh
-l postgres 14.121.70.98 rsync --server -logDtprz --bwlimit=1250 .
/WAL_Archive/

Thanks,

bricklen