Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!mailrus!ulowell!swan!asherman From: asherman@dino.ulowell.edu (Aaron Sherman) Newsgroups: comp.sys.apollo Subject: Re: NFS problem [SCO Unix, executables over NFS] Message-ID: Date: 16 Sep 90 01:06:25 GMT References: <15869@know.pws.bull.com> <644@eba.eb.ele.tue.nl> Sender: news@ul-cs.ulowell.edu Organization: CPE: University of Lowell -- Lowell, MA Lines: 20 In-reply-to: wjw@eba.eb.ele.tue.nl's message of 14 Sep 90 23:51:37 GMT I have discovered that this problem exists with ALL of our SysV machines. If a program which was compiled by the SysV machine is physically located on an Apollo disk which is NFS-mounted, then execution of that program will return the following message: "Killed". On out Stellar GS2000 (running Stellix2.0) the message returned is the same, but a syslog message is also sent out which says that this file had been corupted. My initial guess (to which there is still no confirmation, or denial) is that the file-modification times are being changed on the Apollo end AFTER the file is loaded. -AJS PS: I'm not sure if I posted about this last night, if I did, then sorry about the waste. -- asherman@dino.ulowell.edu or asherman%cpe@swan.ulowell.edu Note that as of 7/18/90 that's asherman@dino.cpe.ulowell.edu "That that is is that that is not is not is that it it is."