If you are looking for a replacement, I don't know of any that do rdiffs
besides rdiff-backup. I think that a good incremental backup would be your
best option.
All incrementals (that I know of) waste space when there are large
files where only a small part of the file changes. This is a
Hi list.
I've posted this problem to a few other lists over the past few days
(rdiff-backup, my local LUG), but I haven't had a reply yet, so I
thought I'd try here.
Short version: rdiff-backup is using 2 GB of memory (1 GB RAM, 1 GB
swap) on one of my backup servers. I'm using the latest Etch
I read you CLUG post. It seems like you should be able to do everything that
you want using rdiff-backup and not using your temp work directory with rsync
(which looks to be messing things up).
Also, if you are using rdiff-backup on backup1, why do you need to preserve
file history on backup2?
Hi there and thanks for your reply.
On Wed, May 7, 2008 at 6:39 PM, Matthew Dale Moore
[EMAIL PROTECTED] wrote:
I read you CLUG post. It seems like you should be able to do everything that
you want using rdiff-backup and not using your temp work directory with rsync
(which looks to be
On Wednesday 07 May 2008 11:58:20 am David wrote:
Also, I don't trust rdiff-backup as much as I do rsync. It seems a bit
too complicated/fragile by comparison. Rsync is very robust, simple,
and works every time. The only reason I use rdiff-backup is because of
it's reverse delta support. I
Hi
Please forgive me as this is my first post but i think i have the format right
;
I have been experiencing problems on my Debian box(2.2r2, sid dist. pIII 500mhz
128mb ram). The problems include 'zombie processes', ie issuing a 'cat' of a
file, and it does not happen, so i have to ctrl+c
On Sun, Sep 30, 2001 at 02:04:12PM +, Dope on Plaztic,,, wrote:
Hi
Please forgive me as this is my first post but i think i have the format
right ;
I have been experiencing problems on my Debian box(2.2r2, sid dist. pIII
500mhz 128mb ram). The problems include 'zombie processes',
hello group knows anyone this problem with the kernel 2.4.1
i do cd /
grep -r hallo *
und then cames a memory enhausted and the network is down.
cu thomas.
To quote Thomas Braun [EMAIL PROTECTED],
# i do cd /
#
# grep -r hallo *
#
# und then cames a memory enhausted and the network is down.
Well, since you're specifying -r, it's going recursively through
subdirectories ... I don't know for sure, but maybe it's running into
some problems with
greetings,
joris
-Original Message-
From: David B. Harris [mailto:[EMAIL PROTECTED]
Sent: Monday, February 19, 2001 2:01 PM
To: debian-user@lists.debian.org
Subject: Re: grep and memory problems with kernel 2.4.1
To quote Thomas Braun [EMAIL PROTECTED],
# i do cd /
#
# grep -r hallo
David B. Harris [EMAIL PROTECTED] writes:
# i do cd /
#
# grep -r hallo *
#
# und then cames a memory enhausted and the network is down.
Well, since you're specifying -r, it's going recursively through
subdirectories ... I don't know for sure, but maybe it's running into
some
To quote Joris Lambrecht [EMAIL PROTECTED],
# the /dev directory indeed just lists a list of names wich are linked
to
# device driver files through the inode table
#
# so in fact you're grep-in the output of the /dev, if this contains
some
# control chars it might hang your grep command, you
Hi,
I've just recently installed Potato on a Compaq Prosignia 300
Server with 64M of RAM. Checking free, however, shows only
13M. The Bios reports the correct amount on startup, and the
previous OS (NT) also had no problems with the memory. I tried
adding an append=mem=64M line to
On Wed, Feb 07, 2001 at 01:33:17PM -0500, Ian Smith wrote:
Hi,
I've just recently installed Potato on a Compaq Prosignia 300
Server with 64M of RAM. Checking free, however, shows only
13M. The Bios reports the correct amount on startup, and the
previous OS (NT) also had no problems
On Wed, Feb 07, 2001 at 01:33:17PM -0500, Ian Smith wrote:
Hi,
I've just recently installed Potato on a Compaq Prosignia 300
Server with 64M of RAM. Checking free, however, shows only
13M. The Bios reports the correct amount on startup, and the
previous OS (NT) also had no problems
Ian Smith wrote:
Hi,
I've just recently installed Potato on a Compaq Prosignia 300
Server with 64M of RAM. Checking free, however, shows only
13M. The Bios reports the correct amount on startup, and the
previous OS (NT) also had no problems with the memory. I tried
adding an
Hi... Several days ago I recompiled my kernel with support for apmd, sound
and some other things. But since I did that, I've had several problems with
my computer's memory. For example, The Myth II Game won't run and my just
installed xmms Mp3 player will skip a lot. Did I do anything wrong?
I fount out it wasn't a complilation problem but a problem with Loadlin.
NOw I have to boot from floppy because I don't want ot mess up witl LILO.
---Hi... Several days ago I recompiled my kernel with support
for apmd, sound and some other things. But since I did that, I've had
I'm using a laptop which only has 4Mb of RAM (640k standard, 3Mb
extended). Despite this I've been having lot's of fun with it. It swaps
a lot, and then today I noticed that top and free only show 2Mb of RAM!
The BIOS check is fine and it used to run Windoze 3.1 ok. Any idea why
the extra memory
Matthew Collins wrote:
[...]
I have a hard enough time remembering the name of things I've
installed. :)
I know the feeling. Try typing `dpkg -l' and you will see what you
installed.
Eric
--
E.L. Meijer ([EMAIL PROTECTED]) | tel. office +31 40 2472189
Eindhoven Univ. of
Can someone point me to the webpage that gives a list of things to
check when you get sporadic segfaults from kernel compiles and the
like? I think I might have a defective RAM chip (ECC RAM at that) and
wanted to check out the possibilities.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the
On Tue, Jan 20, 1998 at 08:32:30AM -0500, Ben Pfaff wrote:
Can someone point me to the webpage that gives a list of things to check
when you get sporadic segfaults from kernel compiles and the like? I
think I might have a defective RAM chip (ECC RAM at that) and wanted to
check out the
On Tue, Jan 20, 1998 at 08:32:30AM -0500, Ben Pfaff wrote:
Can someone point me to the webpage that gives a list of things to check
when you get sporadic segfaults from kernel compiles and the like? I
think I might have a defective RAM chip (ECC RAM at that) and wanted to
check
- I had problems too adding 2*16MB (32MB) and my solution was to
- take out the two 16MB cards.
- I set a little cron job to run memtest at 5 minutes, and every
- time I got a disk problem (could'nt get a free inode, or smthg like) I
- also got a memory error.
- It's now 4 days w/o
Hello,
I am using debian 1.3 with a p166+.
I used to have 16 Mb (2*8) of 60 ns EDO memory and I had no problems.
I bought 32 Mb (2*16) of 60 ns EDO Memory (not the same as above).
So I have now 48 Mb of memory.
It seems to have no problems with Windows
On Fri, 25 Jul 1997, Franck LE GALL - STAGIAIRE A FT.BD/CNET/DTD/PIH wrote:
Hello,
Hi,
It seems to have no problems with Windows NT4.0 but when I run Linux,
I have got disks problems (too much inods...).
I had problems too adding 2*16MB (32MB) and my solution was to
Franck LE GALL - STAGIAIRE A FT.BD/CNET/DTD/PIH [EMAIL PROTECTED] writes:
I used to have 16 Mb (2*8) of 60 ns EDO memory and I had no problems.
I bought 32 Mb (2*16) of 60 ns EDO Memory (not the same as above).
So I have now 48 Mb of memory.
It seems to have no problems
27 matches
Mail list logo
