Date: Thu, 12 Nov 2009 18:53:25 +0100 From: "Matthias Andree" <matthias.andree@gmx.de> To: "Tom Evans" <tevans.uk@googlemail.com>, freebsd-fs@freebsd.org Subject: Re: HEADS UP: Important bug fix in ZFS replay code! Message-ID: <op.u3amnbpw1e62zd@balu.cs.uni-paderborn.de> In-Reply-To: <2e027be00911120623v2019be2euc48a6f0ec9a049a6@mail.gmail.com> References: <200911102227.nAAMRXTf073603@svn.freebsd.org> <20091110224524.GC3194@garage.freebsd.pl> <op.u3ack6yd1e62zd@balu.cs.uni-paderborn.de> <2e027be00911120623v2019be2euc48a6f0ec9a049a6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 12.11.2009, 15:23 Uhr, schrieb Tom Evans <tevans.uk@googlemail.com>:
>> 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 :)
That's the subtle difference between "+" and "\;" at the end if using '{}'
:)
--
Matthias Andree
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.u3amnbpw1e62zd>