Date: Sat, 27 Jan 1996 20:01:40 +0100 (MET) From: Wilko Bulte <wilko@yedi.iaf.nl> To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Subject: vi bug? Message-ID: <199601271901.UAA07337@yedi.iaf.nl>
next in thread | raw e-mail | index | archive | help
I think I stumbled on a vi bug: When /tmp gets full, vi will abort with a message telling what happened. Unfortunately, it leaves /var/tmp/vi.recover files sitting around: # ls -l total 21504 -rwx------ 1 root bin 0 Jan 27 19:16 vi.006980 -rwx------ 1 root bin 0 Jan 27 19:16 vi.006982 -rwx------ 1 root bin 7307264 Jan 27 19:18 vi.006985 -rwx------ 1 root bin 3817472 Jan 27 19:56 vi.007269 In my case /var is on the root fs (as is /tmp). I'd think when vi aborts it can safely rm the recover files (an edit session was never started in the first place, so a recover is not called for). Thoughts? Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands --------------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601271901.UAA07337>