Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 16 Jan 2003 09:14:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 16 Jan 2003 09:14:28 -0500 Received: from chaos.analogic.com ([204.178.40.224]:11657 "EHLO chaos.analogic.com") by vger.kernel.org with ESMTP id ; Thu, 16 Jan 2003 09:14:27 -0500 Date: Thu, 16 Jan 2003 09:25:10 -0500 (EST) From: "Richard B. Johnson" Reply-To: root@chaos.analogic.com To: Linux Geek cc: linux-kernel Subject: Re: Tar'ing /proc ??? In-Reply-To: <3E26BF92.3020303@ToughGuy.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 16 Jan 2003, Linux Geek wrote: > > > Richard B. Johnson wrote: > > >Normally, you do `tar -clf` > > |________ stay on the same file-system. > >Otherwise toy need to use --exclude /proc. Proc is a virtual > >file-system that contains things like kcore. You can get into > >a deadlock when reading kcore and you don't want this in your > >backup anyway. > > > > > > > > > so it means, I can read /proc , write through sysctl interface but no > 'copy' business ;-) . Well you can use `cp` or `cat` because they don't use large amounts of data that gets extended by calling the kernel to set the break address (which can cause a deadlock). `tar` keeps allocating more memory when it reads this large 'file'. Cheers, Dick Johnson Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips). Why is the government concerned about the lunatic fringe? Think about it. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/