"... being used by another person or program."

[Slougi]

louai@Gondolin louai $ mkdir test
louai@Gondolin louai $ cd test/
louai@Gondolin test $ ls
louai@Gondolin test $ touch file1 file2 file3
louai@Gondolin test $ ls
file1  file2  file3
louai@Gondolin test $ gvim file1 
louai@Gondolin test $ gedit file2 &
[1] 7070
louai@Gondolin test $ xedit file3 &
[2] 7094
louai@Gondolin test $ ls
file1  file2  file3
louai@Gondolin test $ rm *
louai@Gondolin test $ ls
louai@Gondolin test $

Well?

[az]

User Friendly

AZ

[thop]

what slougi demonstrated is that linux does not lock you out from deleting a file even it's been used at the time you want to delete it.

[Gurm]

On his machine, under his circumstances, yes.

On my machine, on many machines, under many circumstances... not so.

- Gurm

[Kooldino]

*can't decide whether to get Wholockme or Sysinternals*

[Gurm]

I tried both.

wholockme suffers from two diseases...

1. The "right click menu corruption disease". Picaview used to do this too. Bleh.

2. The "I only work when I feel like it disease".

It's more convenient, to be sure, but Sysinternals has a search function, so...

- Gurm

[Marshmallowman]

I have seen the linux rm thing.

When you rm somthing thats locked it will just return with no message.
But if its not locked and it does delete it, it will say that "xxx has been deleted"

So if does nothing it says nothing, if it does delete it tells you, I can deal with that

[Slougi]

rm has never returned any message when it has deleted something... And I have never seen a locked file in Linux, since UNIX locks are very different from windows locks. Basically what it does is set a flag that the file is in use, but you can still remove it (use -f).