Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!udel!haven!mimsy!nocusuhs!nmrdc1!rdc30
From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson)
Newsgroups: comp.os.minix
Subject: Re: Help needed in elvis editor
Message-ID: <1991Mar5.125545.19045@nmrdc1.nmrdc.nnmc.navy.mil>
Date: 5 Mar 91 12:55:45 GMT
References: <1991Feb27.155309.28624@hoss.unl.edu> <6UR9P_1@xds13.ferranti.com>
Organization: Naval Medical Research & Development Command
Lines: 22

In article <6UR9P_1@xds13.ferranti.com> peter@ficc.ferranti.com (Peter da Silva) writes:
>In article <1991Feb27.155309.28624@hoss.unl.edu> behera@hoss.unl.edu (Siddharth Behera) writes:
>> 	After this I can login again and work.  But the file which I was
>> working on is busy.  That is if I try to open the file by elvis I see a 
>> message appearing on the terminal "file xxx is busy", where xxx is the file
>> I was editing. ...
>
>Elvis creates a temp file in /tmp with the name based on the device and
>inode number of the file. Any file with that device and inode number will
>be "busy". This was a reasonable design choice for a single user system,
>I guess, but the consequences should be better spelled out in the
>documentation.
>
>Remove the file in /tmp and the problem will go away.

Or, if you don't want to lose your work in progress, use virecover to continue
editing the file where you left off when elvis crashed.
-- 
Mike Dobson, Sys Admin for      | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30
AT&T 3B2/600G Sys V R 3.2.2     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
WIN/TCP for 3B2                 | MCI-Mail: 377-2719 or 0003772719@mcimail.com