Hello!
> So, I still think that at the moment there is NO (neither kernel nor
> userspace) way to close a given process' file descriptor. To do that one
> needs to (at least, there are lots of other issues!) enhance the lock
> subsystem to get rid of all references to 'current' context (used for
> deadlock avoidance detection, presumably). The only thing that *can* be
> done now is to switch a reference to a file to another file from a
> specially written filesystem for this very purpose. This will leak a
> little memory until the POSIX locks are fixed but is the best one can do
> for now.
Is there any reason to close FD's of other processes except for debugging?
Have a nice fortnight
-- Martin `MJ' Mares <mj@ucw.cz> <mj@suse.cz> http://atrey.karlin.mff.cuni.cz/~mj/ "Application WINDOWS caused error 0: `No error' and will be aborted."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:26 EST