You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, one may be forced to work with a read-only root filesystem, like the rescue mode mentioned in issue #63. However, I cannot find an easy way to tell nvi2 to not create temporary and recovery files. I've tried the followings:
nvi -F <file>
nvi -c 'set dir=""' <file>
but with no luck... A workaround is to use something like TMPDIR=<writable-directory> nvi <file>. Is there a simpler/cleaner way to deal with this issue? Maybe options to disable temporary file or recovery file or both?
Regards,
Aaron
The text was updated successfully, but these errors were encountered:
However, I still have the same issue. I've tried the following usages:
nvi -c 'set directory="" recdir=""' <file>
nvi -c 'unset directory recdir' <file>
The error messages are:
Error: /var/tmp/vi.recover/: Read-only file system
Modifications not recoverable if the session fails
Error: <file>: Read-only file system
Error: Unable to create temporary file: Read-only file system
Were my usages wrong? Could you please suggest a clearer usage? Thanks.
Rereading you issue, your workaround seems to be correct; I did not mean for disabling TMPDIR. The recdir can be disabled, but there has to be some TMPDIR, because nvi2 (and all nvi variants) need a file system fd to put Berkeley DB file. Does env TMPDIR=. work? If you feel that's still not automatic enough, then we can add some fallback when / is readonly.
Hi.
Sometimes, one may be forced to work with a read-only root filesystem, like the rescue mode mentioned in issue #63. However, I cannot find an easy way to tell nvi2 to not create temporary and recovery files. I've tried the followings:
nvi -F <file>
nvi -c 'set dir=""' <file>
but with no luck... A workaround is to use something like
TMPDIR=<writable-directory> nvi <file>
. Is there a simpler/cleaner way to deal with this issue? Maybe options to disable temporary file or recovery file or both?Regards,
Aaron
The text was updated successfully, but these errors were encountered: