Commit 3d5b5edd authored by ben's avatar ben

Misc changes (ok I forget)


git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup@84 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109
parent fd2c90b0
...@@ -20,6 +20,9 @@ syntax". What's happening?</a></li> ...@@ -20,6 +20,9 @@ syntax". What's happening?</a></li>
<li><a href="#remove_dir">My backup set contains some files that I just realized I don't want/need backed up. How do I remove them from the backup volume to save space?</li> <li><a href="#remove_dir">My backup set contains some files that I just realized I don't want/need backed up. How do I remove them from the backup volume to save space?</li>
<li><a href="#redhat">How do I install the RPMs on Redhat linux system?</a></li> <li><a href="#redhat">How do I install the RPMs on Redhat linux system?</a></li>
<li><a href="#solaris">Under Solaris, rdiff-backup keeps failing with the error message "open(/dev/zero): Too many open files".</a></li>
</ol> </ol>
<h2>FAQ</h2> <h2>FAQ</h2>
...@@ -171,13 +174,50 @@ the above steps (this is what I did). Because of all the dependencies ...@@ -171,13 +174,50 @@ the above steps (this is what I did). Because of all the dependencies
it is usually easier to use source RPMs for this. it is usually easier to use source RPMs for this.
</li> </li>
<P>
<a name="solaris">
<li><strong>Under Solaris, rdiff-backup keeps failing with
the error message "open(/dev/zero): Too many open files".</strong>
<P>Kevin Spicer reported this problem and then posted the following
update:
<pre>
Subject: RE: Crash report....still not^H^H^H working
From: "Spicer, Kevin" <Kevin.Spicer@bmrb.co.uk>
Date: Sat, 11 May 2002 23:36:42 +0100
To: rdiff-backup@keywest.Stanford.EDU
Quick mail to follow up on this..
My rdiff backup (on Solaris 2.6 if you remember) has now worked
reliably for nearly two weeks after I added...
ulimit -n unlimited
to the start of my cron job and created a wrapper script on the remote
machine which looked like this...
#!/bin/sh
ulimit -n unlimited
rdiff-backup --server
exit
And changed the remote schema on the command line of rdiff-backup to
call the wrapper script rather than rdiff-backup itself on the remote
machine. As for the /dev/zero thing I've done a bit of Googleing and
it seems that /dev/zero is used internally by libthread on Solaris
(which doesn't really explain why its opening more than 64 files - but
at least I think I've now got round it).
</pre>
</li>
</ol> </ol>
<hr> <hr>
<a href="http://www.stanford.edu/~bescoto">Ben Escoto</a> <address><a href="mailto:bescoto@stanford.edu">&lt;bescoto@stanford.edu&gt;</a></address> <a href="http://www.stanford.edu/~bescoto">Ben Escoto</a> <address><a href="mailto:bescoto@stanford.edu">&lt;bescoto@stanford.edu&gt;</a></address>
<!-- Created: Fri Sep 7 15:34:45 PDT 2001 --> <!-- Created: Fri Sep 7 15:34:45 PDT 2001 -->
<!-- hhmts start --> <!-- hhmts start -->
Last modified: Mon Apr 29 23:59:11 PDT 2002 Last modified: Sat May 11 19:26:17 PDT 2002
<!-- hhmts end --> <!-- hhmts end -->
</body> </body>
</html> </html>
...@@ -5,14 +5,14 @@ logging stats ...@@ -5,14 +5,14 @@ logging stats
Add to above Dean Gaudet's suggestion: make errors look prettier (like tar). Add to above Dean Gaudet's suggestion: make errors look prettier (like tar).
Add new restore option - bring directory to state it was in, say, 5 Examine certain network settings like Globals.conn_bufsize and whether
days ago, etc. or not ssh is used with compression, and find good defaults or add
easy to use switches.
Michael S. Muegel suggestion: "--char-translate source-char Examine and fix recovery problems.
replacement-string" for use between windows/unix conversions, e.g. ':'
to _colon_. Also distinguish new vs changed update in lvl 5 logging.
Add options to pass to ssh (e.g. compression, maybe arbitrary options).
Bugs: Think about adding Gaudet's idea for keeping track of renamed files.
Jamie Heilman's race condition --read-only and --write-only /usr/foo switches to tighten security up some.
\ No newline at end of file
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment