Time rsYnc Machine (tym)

Dan Stromberg drsalists at gmail.com
Sat Jul 28 13:31:52 MDT 2012


Not being interactive is important for running in cron; I believe stdin
will probably immediately EOF.

But redirecting  stdout and stderr is unnecessary - the output just goes to
a cron e-mail with most cron's.   Sometimes it's better to redirect to a
file, but  that's more of a user preference things.

On Sat, Jul 28, 2012 at 12:26 PM, <josephj at main.nc.us> wrote:

> 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 <ca at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/rsync/attachments/20120728/68219732/attachment.html>

More information about the rsync mailing list