Messages in this thread | | | From | RAMON_GARCIA_F <> | Date | Mon, 21 Jul 2003 18:55:24 +0200 | Subject | Re: Suggestion for a new system call: convert file handle to a cookie for transfering file handles between processes. |
| |
My proposal is useful for cases where the server program is running with a different priviledge from the user invoking it. Examples where this behaviour is useful are writting CDs, saving man pages, saving TeX cache files, where full access to a resource would be unsafe, but limited access through an intermediate server is safe.
In addition, this proposal is useful for cases where the server process cannot access the named file, becaue it does not have permission to do so, or because it is anonymous (example: a pipe).
I can't see why cookies introduce circular references. A cookie referes to an inode, but an inode does not refer to a file.
However, a cookie introduces a permanent reference to a file handle. This reference is not destroyed until the cookie is used. Therefore, cookies should have a timeout associated with them, so that if they are not consumed they should be destroyed.
Ramon
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |