Date: Thu, 15 Mar 2007 14:37:30 -0400 From: John Nielsen <lists@jnielsen.net> To: freebsd-questions@freebsd.org Cc: Bram Schoenmakers <bramschoenmakers@xs4all.nl> Subject: Re: 'nodump' on directories: new contents still dumped Message-ID: <200703151437.30390.lists@jnielsen.net> In-Reply-To: <200703151857.19679.bramschoenmakers@xs4all.nl> References: <200703151857.19679.bramschoenmakers@xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 15 March 2007 13:57, Bram Schoenmakers wrote: > I'm using dump(8) for backing up a FreeBSD 4.10 server. In order to > decrease the resulting file size, I flagged some directories like > /usr/ports and /usr/src with 'nodump'. I adjusted the dump level 0 script > to have -h 0, so that worked fine. The other scripts for dumps >0 do not > have a -h flag set, because -h 1 is default. > > The problem is that new files appearing in the /usr/ports tree (daily > portsnap cron) do not have the 'nodump' flag set. But despite the 'nodump' > flag on the /usr/ports directory, the new files in the tree are still > dumped. > > I understood that dump does not enter directories with 'nodump' flag set, > so it shouldn't see the new files inside, right? Or is this behavior > implemented in a newer version than FreeBSD 4.10? I have scanned the CVS > logs for dump, but couldn't find anything relevant. Read the dump manpage more carefully, and pay particular attention to the -h flag. You probably want '-h0'. JN
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200703151437.30390.lists>