Messages in this thread |  | | | Date | Fri, 24 Sep 2004 14:41:35 -0600 | | From | Chris Friesen <> | | Subject | Re: mlock(1) |
| |
Chris Wright wrote:
> 2. Problem is the execve(2) that the mlock(1) program would have to call. > This blows away the mappings which contain the locking info.
Does it? The man page said it isn't inherited on fork(), but why wouldn't it be inherited on exec()?
Chris - 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/
|  |