I glanced at the source code, and it appears pretty trivial (a change to
options.c and a change to backup.c) to implement a user-selected backup
script. All it appears to involve is adding an option to the command
line and an extra if statement in backup.c
I might give it a shot in my ample
> "yan" == yan seiner <[EMAIL PROTECTED]> writes:
yan> I've been trying to come up with a scripting solution for
yan> this for some time, and I'm convinced there isn't one.
yan> You definitely want to handle the revisions in the same way
yan> as logrotate: keep a certain dept
Administrator
Division of Entomology CSIRO
GPO Box 1700
Canberra ACT 2601
ph 02 6246 4391
fax 02 6246 4000
-Original Message-
From: Martin Pool [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 22 March 2001 1:17 PM
To: Sean J. Schluntz
Cc: [EMAIL PROTECTED]
Subject: Re: unlimited backup
"Sean J. Schluntz" <[EMAIL PROTECTED]> wrote:
>
> >Maybe the solution is a --backup-script= option, that would call an
> >external script and hand it the filename. That way, each user could
> >customize it to their heart's content.
>
> Now I though about that, but it seems like a way to real
>Maybe the solution is a --backup-script= option, that would call an
>external script and hand it the filename. That way, each user could
>customize it to their heart's content.
Now I though about that, but it seems like a way to really pound your system.
Like doing a find -exec, if there ar
In message <[EMAIL PROTECTED]>, Mike Lang writes:
>Sounds like you want rsync to be CVS, or maybe CVS to have an rsync module.
>
>How about rsync then run a script to do a cvs commit?
How well does CVS deal with binary files? What would the change log look
like for a JPG that has been updated o
The little bit I know of CVS, it's overkill for what I need. CVS keeps
a revision history, authors, etc.
All I need is for something (maybe an external archive script to rsync?)
to:
delete the oldest backup
rotate the remaining backups
create the new backup with a .1
Maybe the solution is a --b
Sounds like you want rsync to be CVS, or maybe CVS to have an rsync module.
How about rsync then run a script to do a cvs commit?
--Mike
At 10:33 AM 3/22/01 -0500, Yan Seiner wrote:
>OK, but I'm trying to do is to keep the last n revisions - NOT the last
>n weeks.
>
>So what if I ha
ay
> [EMAIL PROTECTED]
> 303.682.4917
> Philips Semiconductor - Colorado TC
> 1880 Industrial Circle
> Suite D
> Longmont, CO 80501
>
> [EMAIL PROTECTED]@[EMAIL PROTECTED] on 03/22/2001 03:17:35 AM
> Sent by:[EMAIL PROTECTED]
> To: [EMAIL PROTECTED]@SMTP
&
script it.
Tim Conway
[EMAIL PROTECTED]
303.682.4917
Philips Semiconductor - Colorado TC
1880 Industrial Circle
Suite D
Longmont, CO 80501
[EMAIL PROTECTED]@[EMAIL PROTECTED] on 03/22/2001 03:17:35 AM
Sent by:[EMAIL PROTECTED]
To: [EMAIL PROTECTED]@SMTP
cc:
Subject:
I've been trying to come up with a scripting solution for this for some time, and
I'm convinced there isn't one.
You definitely want to handle the revisions in the same way as logrotate: keep a
certain depth, delete the oldest, and renumber all the older ones.
If you want to get real ambitius, y
On 22 Mar 2001, Alberto Accomazzi <[EMAIL PROTECTED]> wrote:
> -V, --version-control=WORD override the usual version control
>
> The backup suffix is ~, unless set with SIMPLE_BACKUP_SUFFIX. The
> version control may be set with VERSION_CONTROL, values are:
>
> t, numbered make number
In message <[EMAIL PROTECTED]>, "Sean J. Schluntz" writes:
>
> >> That's what I figured. Well, I need it for a project so I guess you all
> >> won't mind if I code it and submit a patch ;)
> >>
> >> How does --revisions=XXX sound. --revisions=0 would be unlimited, any oth
er
> >> number would
>> That's what I figured. Well, I need it for a project so I guess you all
>> won't mind if I code it and submit a patch ;)
>>
>> How does --revisions=XXX sound. --revisions=0 would be unlimited, any other
>> number would be the limiter for the number of revisions.
>
>And when it reaches that
On 21 Mar 2001, "Sean J. Schluntz" <[EMAIL PROTECTED]> wrote:
>
> >> Sorry is this is a repeat, but there is no search option (that I can find)
> >> on the list server.
> >>
> >> Is there a way to make rsync keep unlimited backup copies. When ever a file
> >> is changed for it to (with out any o
On 21 Mar 2001, "Sean J. Schluntz" <[EMAIL PROTECTED]> wrote:
>
> Sorry is this is a repeat, but there is no search option (that I can find)
> on the list server.
>
> Is there a way to make rsync keep unlimited backup copies. When ever a file
> is changed for it to (with out any of the file merg
Sorry is this is a repeat, but there is no search option (that I can find)
on the list server.
Is there a way to make rsync keep unlimited backup copies. When ever a file
is changed for it to (with out any of the file merge stuff going) just push
the earler backups down a counting number and dr
17 matches
Mail list logo