Re: mlock(1)

[Ryan Cumming]

On Friday 24 September 2004 13:41, Chris Friesen wrote:
> 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()?
>
From my mlock(2) manpage:
"...they are guaranteed to stay in RAM until the pages are unlocked by munlock 
or munlockall, until the pages are unmapped via munmap, or until the process 
terminates or starts another program with exec."

-Ryan

Attachment: pgp00000.pgp
Description: PGP signature