Linux: page errors and network file systems

Question

If physical memory runs out on a Linux system, does it throw inactive executable code pages? I believe the answer is yes, because there is no reason to keep them in a swap, so they are simply discarded and reloaded if necessary (as far as I know, this is what FreeBSD does).

If this is true for Linux, my question is, how does it handle executable files launched from network file systems (e.g. NFS)? Does it do and retrieve executable pages over the network if there is a page error?

Answer 1

If the Linux system runs out of physical memory, is it inactive executable code pages? I assume that the answer is yes, since there is no reason to keep them in exchange, so they are simply discarded and rebooted if necessary (as far as I know, this is what FreeBSD does).

Yes Yes.

If this is true for Linux, my question is, how does it handle executable files being launched from a network of file systems (like NFS)? Does it go and extract executable pages on top of the network if there is a page error?

The NFS client caches stuff locally (if you are concerned about speed), but maybe not the whole file (if you are concerned about consistency). Here is the NFS FAQ link .