From owner-freebsd-isp Mon Aug 14 7:22: 9 2000 Delivered-To: freebsd-isp@freebsd.org Received: from black.purplecat.net (ns1.purplecat.net [209.16.228.148]) by hub.freebsd.org (Postfix) with ESMTP id 10FDD37C1B9 for ; Mon, 14 Aug 2000 07:22:00 -0700 (PDT) (envelope-from pbrezny@purplecat.net) Received: from sargent (ci377160-a.ashvil1.nc.home.com [24.15.65.209]) by black.purplecat.net (8.8.8/8.8.8) with SMTP id KAA00253 for ; Mon, 14 Aug 2000 10:23:34 -0400 (EDT) (envelope-from pbrezny@purplecat.net) Reply-To: From: "Peter Brezny" To: Subject: Backup restore problem with permissions and bzip2 Date: Mon, 14 Aug 2000 10:21:24 -0400 Message-ID: <000301c005fa$edaee980$cc01a8c0@sargent> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Recently I ran into trouble using the fp_install.sh script when adding a virtual domain on a freebsd 2.2.8/apache-fp system. For some reason, instead of chowning the single directory to the new user, it chowned the entire web directory, so now all of my customer's directories are owned by the wrong person. :| I figured the best thing to do would be to restore the entire directory from backup to get the correct permissions back, so using bunzip2 < /bkup/wkbkup.home.tar.bz2 | tar xvf - home/www/data/* I restored all the directories from yesterday's backup. However, the permissions were not restored. Looking through the man page, both tar and bzip2 say that they will restore permissions. What have I done wrong here and is there a way to restore _just_ the permissions as opposed to all the content in each directory as well? To compound matters, I've noticed that the superblock clean flag is not being set on a reboot. fsck doesn't seem to be able to fix it. If anyone knows of more thorough diagnostic programs or ideas on what might be causing this I'd be very grateful. Thanks in advance. Peter Brezny purplecat.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message