Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!crcnis1.unl.edu!wupost!spool.mu.edu!olivea!mintaka.lcs.mit.edu!ai-lab!hal.gnu.ai.mit.edu!mycroft From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum) Newsgroups: comp.os.386bsd.questions Subject: Re: Executables + NFS == weird problems Message-ID: <1nhn07INN57h@life.ai.mit.edu> Date: 9 Mar 93 09:11:35 GMT References: <1993Mar3.114201.5316@amsteel.chel.su> Organization: /etc/organization Lines: 21 NNTP-Posting-Host: hal.ai.mit.edu In article <1993Mar3.114201.5316@amsteel.chel.su> ivans@amsteel.chel.su (Mike Ivans) writes: > > When I copy the *same* executable to local fs it runs without errors. There is a weird NFS caching problem with respect to executables. If I run an executable on a NFS-mounted file system, modify it, and run it again, the effect is of running the old one. I suspect that if some pages which were not used before (or which happen to have been garbage collected) are needed the second time, strange things like this will occur. I haven't bothered to track this down yet, but it looks pretty simple. (BTW, *please* don't right-justify your text!) -- \ / Charles Hannum, mycroft@ai.mit.edu /\ \ PGP public key available on request. MIME, AMS, NextMail accepted. Scheme White heterosexual atheist male (WHAM) pride!