Killing the rsync job would work of course, but I thought it
would be better to have the halting ability built-in, so that
it could stop at a "safe" time, between files, say, instead
of being abruptly terminated by an outside process. (But I
suppose rsync is robust enough that it probably doesn't matter?)
John.
-----Original Message-----
From: Sean Berry [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 03, 2001 00:44
To: Allen, John L.
Cc: '[EMAIL PROTECTED]'
Subject: Re: Need for an --operating-window feature ???
Why not just put a job at that given time to kill your rsync process?
On Mon, 2 Apr 2001, Allen, John L. wrote:
> Date: Mon, 2 Apr 2001 16:19:30 -0400
> From: "Allen, John L." <[EMAIL PROTECTED]>
> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> Subject: Need for an --operating-window feature ???
>
> I'm new to rsync, so be gentle... I have need to use rsync, but want
> to have it operate only off-hours when the network is lightly loaded.
> I did not see any option for making rsync obey an "operating time
> window" so that it would basically cease copying data if the time-of-day
> falls outside a specified window. I thus thought it might be a good idea
> to have a --operating-window option where you could specify an
> allowed time of operation by indicating two endpoints, perhaps like this
>
> --operating-window 22:00-05:00
>
> where the times are given in HH:MM 24-hour military time.
> You could obviously extend this to allow for multiple disjoint windows,
> but I don't think there's much point.
>
> Should be easy to code. Any comments?
>
> John.
> --
> John L. Allen, Dept 0631, EMS
> 516-346-8456, MS C72-001
> Logicon
> A Northrop Grumman Company
> --
>
>
>
--
Sean Berry works with many flavors of UNIX, but especially Solaris/SPARC and
NetBSD. His hobbies include graphics and raytracing. He drinks coke
mostly.
His opinions are not necessarily those of his employers.
