He redirects stdout and stderr to files and doesn't require user interaction.
Living on a notebook, almost all of my scripts don't do that, so they won't work from cron or any background situation unless I modify them with that in mind. Joe > On Sat, Jul 28, 2012 at 3:48 AM, M. Carrasco <c...@dragoman.org> wrote: > >> 3. Cron >> It can run properly run from cron as it is demonized. >> > What's this about? I've never had problems running run of the mill > scripts > from cron, once the environment is adequately replicated. > > >> "--hard-links" is not used and there is for and against reasons. From >> man >> rsync: >> >> "... finding multiply-linked files is expensive." >> "Without this option, hard-linked files in the transfer are treated >> as >> though they were separate files." >> > FWIW, it might be nice to add a hardlink detecting bloom filter to rsync > at > some point. This makes the process of detecting hardlinks less expensive. > Another way to narrow down the field is to just look at st_nlink. > -- > Please use reply-all for most replies to avoid omitting the mailing list. > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html