Hi Rhea,

The article has been updated. The use of a cron job has been dismissed and replaced by a Lsyncd configuration file where the local-to-remote file transfer method is rsyncssh. The Lsyncd Daemon now handles the automation of local-to-remote file synchronization tasks.

Hi Fredrick, the article has been updated. The cron job approach has been removed and replaced with a Lsyncd configuration file that answers to a Daemon. We can comfortably conclude that Lsyncd’s local-to-remote directory synchronization is now fully automated and working as it should be.

Alternatively, why is lysncd needed when one could just put an rsync command to synchronize the remove filesystem at a specified interval in cron.d entry? Nowhere in your article do you explain what is the benefit of running lsyncd over that method or its deficiency in having to be activated by a cron job.

In fact when I visit the lsyncd website and read the documentation, nowhere is there mention of using cron — just set up the configuration file with the target director, the time interval, and also the transfer method to use eg rsync or rsyncssh.

*/5 * * * * rsync -avh /home/dnyce/linuxshelltips_localsync/ ubuntu@18.118.208.79:/home/ubuntu/linuxshelltips_remotesync/ 1>/dev/null 2>&1 &

The daemon is not syncing bi-directionally and one would expect a daemon to handle its own scheduling, but even that is farmed out to corn.

So once again, What is the point of this command?