Date: Thu, 12 Nov 2009 14:23:43 +0000 From: Tom Evans <tevans.uk@googlemail.com> To: Matthias Andree <matthias.andree@gmx.de>, freebsd-fs@freebsd.org Subject: Re: HEADS UP: Important bug fix in ZFS replay code! Message-ID: <2e027be00911120623v2019be2euc48a6f0ec9a049a6@mail.gmail.com> In-Reply-To: <op.u3ack6yd1e62zd@balu.cs.uni-paderborn.de> References: <200911102227.nAAMRXTf073603@svn.freebsd.org> <20091110224524.GC3194@garage.freebsd.pl> <op.u3ack6yd1e62zd@balu.cs.uni-paderborn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 12, 2009 at 2:16 PM, Matthias Andree <matthias.andree@gmx.de>wrote:
> Am 10.11.2009, 23:45 Uhr, schrieb Pawel Jakub Dawidek <pjd@freebsd.org>:
>
>
> You can locate such files with the following command:
>>
>> # find / -perm -7777 -print0 | xargs -0 ls -ld
>>
>
> Use ls -ldb to be on the safe side (control characters!).
>
> So how about these refinements:
>
> find / -perm -7777 -exec ls -ldb '{}' +
> find / -perm -7777 -ls (not sure what that does with escapes)
>
>
> You can locate and fix such files with the following command:
>>
>> # find / -perm -7777 -print0 | xargs -0 chmod a-s,o-w,-t
>>
>
> find / -perm -7777 -exec chmod a-s,o-w,-t '{}' +
>
> --
> Matthias Andree
>
>
> -exec causes a fork()/exec() for each file found doesn't it? xargs would be
more efficient (since we're bikeshedding :)
Cheers
Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2e027be00911120623v2019be2euc48a6f0ec9a049a6>