From owner-freebsd-questions@FreeBSD.ORG Thu Mar 15 18:15:03 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 005B716A404 for ; Thu, 15 Mar 2007 18:15:02 +0000 (UTC) (envelope-from bramschoenmakers@xs4all.nl) Received: from smtp-vbr16.xs4all.nl (smtp-vbr16.xs4all.nl [194.109.24.36]) by mx1.freebsd.org (Postfix) with ESMTP id 944F113C465 for ; Thu, 15 Mar 2007 18:15:02 +0000 (UTC) (envelope-from bramschoenmakers@xs4all.nl) Received: from s040391.lan (a80-100-31-69.adsl.xs4all.nl [80.100.31.69]) by smtp-vbr16.xs4all.nl (8.13.8/8.13.8) with ESMTP id l2FHvK2h023646 for ; Thu, 15 Mar 2007 18:57:21 +0100 (CET) (envelope-from bramschoenmakers@xs4all.nl) From: Bram Schoenmakers To: freebsd-questions@freebsd.org Date: Thu, 15 Mar 2007 18:57:19 +0100 User-Agent: KMail/1.9.6 X-Face: &[!|}QvdlkzFIu, |mW.\-Ci1t2d@CEo+#Q14@XM9*@`S, @l*5r-m!\, , kFc:ZlD62]6/>[ Ovg; N[qk; `w6=5abys2!H+EUYcEDJ%lo&d67gO.!/ w@YD{YH]Ebe{@|(qtKgoum%{-=qXlf.+/`^E<'!m"?5d<&C(:B+p*KjP'-Knv!6U<1W!~Z P3ee-{fAb-i+MsJHM@ MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200703151857.19679.bramschoenmakers@xs4all.nl> X-Virus-Scanned: by XS4ALL Virus Scanner Subject: 'nodump' on directories: new contents still dumped X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2007 18:15:03 -0000 Hi, 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. One 'hack' is to run a script prior to the dump to recursively set all 'nodump' flags where appropriate, but I'm hoping that someone can enlighten me what is going on. Thanks in advance, -- Bram Schoenmakers What is mind? No matter. What is matter? Never mind. (Punch, 1855)