From: Jaimie Vandenbergh on
On Sun, 25 Jul 2010 08:16:59 +0100, Chris Ridd <chrisridd(a)mac.com>
wrote:

>To find what has a file open, type "sudo lsof". There's a lot of output...

sudo lsof | grep "name of file concer.ned"

would avoid the irrelevant output. Takes a few seconds to run, during
which the prompt will sit there like a lemon, by the way.

Cheers - Jaimie
--
Isn't it funny how much mature wisdom resembles being too tired to bother?
From: Ben Shimmin on
Jaimie Vandenbergh <jaimie(a)sometimes.sessile.org>:
> On Sun, 25 Jul 2010 08:16:59 +0100, Chris Ridd <chrisridd(a)mac.com>
> wrote:
>>To find what has a file open, type "sudo lsof". There's a lot of output...
>
> sudo lsof | grep "name of file concer.ned"
>
> would avoid the irrelevant output. Takes a few seconds to run, during
> which the prompt will sit there like a lemon, by the way.

opensnoop(1) is also good. You can invoke it like this:

$ sudo opensnoop -a -f FILENAME

b.

--
<bas(a)bas.me.uk> <URL:http://bas.me.uk/>
`Zombies are defined by behavior and can be "explained" by many handy
shortcuts: the supernatural, radiation, a virus, space visitors,
secret weapons, a Harvard education and so on.' -- Roger Ebert
From: Jaimie Vandenbergh on
On Mon, 26 Jul 2010 00:18:16 +0100, Ben Shimmin
<bas(a)llamaselector.com> wrote:

>Jaimie Vandenbergh <jaimie(a)sometimes.sessile.org>:
>> On Sun, 25 Jul 2010 08:16:59 +0100, Chris Ridd <chrisridd(a)mac.com>
>> wrote:
>>>To find what has a file open, type "sudo lsof". There's a lot of output...
>>
>> sudo lsof | grep "name of file concer.ned"
>>
>> would avoid the irrelevant output. Takes a few seconds to run, during
>> which the prompt will sit there like a lemon, by the way.
>
>opensnoop(1) is also good. You can invoke it like this:
>
> $ sudo opensnoop -a -f FILENAME

Oh, nice toy - thanks for that one!

Cheers - Jaimie
--
I think I'm too sarcastic to believe in myself. -- Nietzsche