From owner-freebsd-questions Thu Oct 23 21:57:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA22220 for questions-outgoing; Thu, 23 Oct 1997 21:57:11 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from luke.cpl.net (luke.cpl.net [207.67.172.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA22210 for ; Thu, 23 Oct 1997 21:57:08 -0700 (PDT) (envelope-from shawn@luke.cpl.net) Received: from localhost (shawn@localhost) by luke.cpl.net (8.8.7/8.6.12) with SMTP id VAA28486; Thu, 23 Oct 1997 21:57:51 -0700 (PDT) Date: Thu, 23 Oct 1997 21:57:50 -0700 (PDT) From: Shawn Ramsey To: "Matthew D. Fuller" cc: questions@FreeBSD.ORG Subject: Re: deleted huge directory In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I think that, at some level, I knew there was a limit like that. > In that case, you're going to have some trouble. Maybe do a series of > ls's or echo's, echoing a* > file1, b* > file2, etc, depending on what the > files are named. If an echo * can't work, I'd guess an rm * wouldn't > either. You'll have to find some way to piecemeal this up ( I would say > info files that contain the dir list; my pet project of the night) and rm > 'cat ' for however many files you have. I think someone will have > to give a hint what's in there as far as file names are concerned. The > only news server I have access to doesn't have a directory like that > there. "find /var/news/spool/control/cancel | xargs rm -rf" worked. Well, is working. Its still deleting. :)