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
Martin Pool writes:
> > I was not sure on how to ask a question on the Rsync FAQ page, the only
> > links it had was to answer questions. I saw your email address all over
> > the FAQ page, so I figured I'd try emailing you. Heres my question:
> > The most likely problem is that there is a
>
>
The most likely problem is that there is a
gid = somegroup
entry in your rsyncd.conf that does not correspond to an entry in
/etc/group. For example, you may be trying to set the group to
`nobody', but perhaps DGUX requires `nogroup' or `65533' or something
similar.
--
Martin
- For
> "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
What I would like it to create a backup server that maintains a copy of all
the files on a server and also maintains a copy of 20 or so deltas so that
the last twenty or so revisions can be rebuilt. Is this possible or what
would be the best approach to create such a beast?
--
Ian Willis
Systems
On torsdag 22. mars 2001, 19:39, Dave Dykstra wrote:
> >
> > > rsync version(s)
> >
> > 2.4.1 protocol v. 24
>
> That's your problem. SSH hangs were a known problem in rsync 2.4.1.
> Upgrade to 2.4.6.
>
Right. Some day I will learn to only use last versions. Thanks.
R.
On torsdag 22. mars 2001, 16:21, you wrote:
> Hi Williams,
> You were right, my sshd was not running on host2.
>
> However, when I re-start sshd and run the command I am asked for a root
> password.
> When I run rsync with --rsh option I am NOT prompt for password.
>
> How can I rsync with -e ssh
Thanks Dave that was the problem, Tim Conway helped me with that one. One
other thing I just noticed is:
When I rsync from a linux box to a linux box using:
/usr/bin/rsync -e ssh 'bailey::tst/*' /tmp/
Linux knows the "*" means all, when I'm on my linux box and I try to sync with
the DGUX, the DGUX
On Thu, Mar 22, 2001 at 01:16:15PM -0500, Gerry Maddock wrote:
> I just downloaded the latest rsync and installed it on my DGUX sys. I
> run rsync on all of my linux boxes, and it runs well. Once I had the
> /rsync dir created, wrote an rsyncd.conf in /etc, I started rsync with
> the --daemon opti
On Thu, Mar 22, 2001 at 01:25:37PM +0100, Ragnar Wisløff wrote:
> Robert Scholten skrev:
> > Hi Ragnar,
>
> Wow, that's quick response! Not waiting for Mir to fall on top of you,
> I hope ...
>
> > It's a common (and nagging) problem. Could you post again, with:
>
> :-(
>
> >
> > Machine t
I just downloaded the latest rsync and installed it on my DGUX sys. I
run rsync on all of my linux boxes, and it runs well. Once I had the
/rsync dir created, wrote an rsyncd.conf in /etc, I started rsync with
the --daemon option. Next, from one of my linux boxes, I tried to rsync
files out of my
I asked a friend of mine who has used cvs extensively, and he said:
When adding files to cvs (somewhat equivilent to 'cleartool mkelem ...'),
you must tell cvs to treat a file as binary using the -kb flag, and/or
set global defaults for different file types (e.g., *.jpg) using a
cvswrappers fi
"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
OK, but I'm trying to do is to keep the last n revisions - NOT the last
n weeks.
So what if I have a file that changes once every 6 weeks? I want to
keep 4 revisions, so that means I have to go back 6 months.
But now the file next to it gets updated daily
You see my problem?
I want to
Hi Williams,
You were right, my sshd was not running on host2.
However, when I re-start sshd and run the command I am asked for a root
password.
When I run rsync with --rsh option I am NOT prompt for password.
How can I rsync with -e ssh without being prompt for a password? I run the
commands
There isn't one?
rsync has the --backup-dir= option.
keep each set of backups to a different directory, then merge them back into the main
heirarchy if needed. Since they're already sifted out, it'd be easy to archive them,
as well.
if it's a daily, --backup-dir=$(( $(date +%j) % 28 )) will kee
Magda,
Problem 1 here is caused by sshd either not running
or not being installed on the receiving host (host2).
If you login to host2 and start up sshd you should be
in pretty good shape.
-Original Message-
From: Magdalena Hewryk [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 22, 200
Hi,
I'm trying to use the "ssh" option instead of "rsh" but I am getting some
errors.
Below are examples:
1.
# /usr/local/bin/rsync --rsync-path=/usr/local/bin/rsync -av -e ssh
/tmp/hello root@host2:/tmp
Secure connection to host2 refused; reverting to insecure method.
Using rsh. WARNING: Connec
I get the same thing when I use Rsync on BSD/OS 4.2 to mirror two hard
drives.
If there are a lot of files, it will get stuck and then I usually have to
CTRL+C it and start again.
The machine has plenty of RAM and free space.
- Vinay Bharel <[EMAIL PROTECTED]>
On Thu, 22 Mar 2001, Ragnar [iso
Robert Scholten skrev:
> Hi Ragnar,
Wow, that's quick response! Not waiting for Mir to fall on top of you,
I hope ...
> It's a common (and nagging) problem. Could you post again, with:
:-(
>
> Machine type(s)
2 x Dell PowerEdge 2450 (identical)
> Operating system(s)
Red Hat Linux 6.2,
Hello list members,
I've come up against an rsync problem which I hope someone here can
help me with.
Running rsync to transfer a relatively large number of files causes
rsync to freeze during transfer. I'm running rsync from the command
line, no daemon or any such stuff. This is the command:
What happens if you do a "dry run", i.e. with the -n option? That way you
can tell if it's network-related. I've found that network speed with
cygwin stuff is pretty sad. For example, using Tridge's socklib network
speed test (bewdiful - thanks Tridge!), I get 2MB/s under Win2k+cygwin,
vs. 10MB/
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
Hello !
I want to do a backup of some Win98-Workstations to a Linux-Server. I
compiled rsync for Windows using Cygwin 1.18 and the instructions in
win95.txt. All worked fine, but it is terribly slow !!!
For testing purposes I took two machines, one with linux, the other
with linux and win98. I w
28 matches
Mail list logo