From owner-freebsd-questions Tue Jul 4 17:53:24 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id B33FD37BBC6 for ; Tue, 4 Jul 2000 17:53:11 -0700 (PDT) (envelope-from jcwells@nwlink.com) Received: from utah (jcwells@utah.nwlink.com [209.20.130.41]) by smtp.nwlink.com (8.9.3/8.9.3) with SMTP id RAA04277; Tue, 4 Jul 2000 17:52:54 -0700 (PDT) Date: Tue, 4 Jul 2000 18:04:35 -0700 (PDT) From: "Jason C. Wells" X-Sender: jcwells@utah To: Christoph Sold Cc: Alan Clegg , Christoph Sold , FreeBSD-Questions@FreeBSD.ORG Subject: Re: find -exec Problem In-Reply-To: <3960FEA2.FD01F3DE@i-clue.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Jul 2000, Christoph Sold wrote: > > find . -type d -print -exec 'chmod o+rx {}' \; > > Nope. Problem remains. Yeah I'm running bash here. Did you leave a space before the slash? I have been confounded by this as well. You would think the space doesn't matter but for me it did. Later, Jason C. Wells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message