From d84f2470c3a67a1b8f021c4b308c9c4c9465387e Mon Sep 17 00:00:00 2001 From: Sheldon Hearn Date: Fri, 11 Aug 2000 10:37:39 +0000 Subject: [PATCH] Add text from NetBSD's rev 1.12 which should have accompanied the changes made to our own source on 1997-01-01. PR: 20445 Submitted by: Jon Masami Kuroda --- sbin/restore/restore.8 | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/sbin/restore/restore.8 b/sbin/restore/restore.8 index f91184c79eed..af81e8661499 100644 --- a/sbin/restore/restore.8 +++ b/sbin/restore/restore.8 @@ -444,6 +444,28 @@ To do a network restore, you have to run restore as root. This is due to the previous security history of dump and restore. (restore is written to be setuid root, but we are not certain all bugs are gone from the restore code - run setuid at your own risk.) +.Pp +The temporary files +.Pa /tmp/rstdir* +and +.Pa /tmp/rstmode* +are generated with a unique name based on the date of the dump +and the process ID (see +.Xr mktemp 3 ), +except for when +.Fl r +or +.Fl R +is used. +Because +.Fl R +allows you to restart a +.Fl r +operation that may have been interrupted, the temporary files should +be the same across different processes. +In all other cases, the files are unique because it is possible to +have two different dumps started at the same time, and separate +operations shouldn't conflict with each other. .Sh HISTORY The .Nm restore