As files are backed up, backup also stores the file owner ID number, permissions, and timeldate stamp of the file. This is used by restore when retrieving the files. After the files are restored, they appear just as they were at the time of the backup. The user should be aware of several potential problems.
One problem is that it is possible for users with identical ID numbers to exist on different systems with different names. Since only the owner ID number is saved with the file, not the owner's name, when the file is restored, the owner will be the name of the user in the password file that matches the ID number. If the user ID number does not exist in the restoring system password file, the owner of the file will be the ID number enclosed in double angle brackets, for example,
<<14». Secondly, file permissions are respected during restore. If the restoring user does not have write permission for a file, it will not be restored. One method to facilitate easy movement of files among many machines is to always backup and restore the files from the public user, which exists on all machines. In any event, the user system can backup and restore any file as well as change ownership and permissions.
USER COMMANDS restore
MESSAGES
Catalog of backup on <file_name>
Restore backup from <file name>
These messages are printed when restore begins-:- They notify you of the function about to be performed.
Several of the following messages prompt you for a positive or negative response. The program interprets any response that does not begin with an upper or lowercase "n" as a positive response.
Restore <file_name> (yin)?
If you specify the "p" option, the program prints one of these prompts before it takes any action.
A response of "n" or "N" indicates that the operation should not be performed for the given file.
Any other response is interpreted as yes.
Insert next volume - Hit CIR to continue:
This prompt is issued when the program needs a new backup volume. You should type a carriage return only when the next volume has been placed in the device.
link <file name 1> to <file name 2>
copy <file_name>
Copying from <dir_name>
The program prints these messages as it takes the corresponding action during a creation operation.
This is Volume f<number 1> -- Expected Volume f<number 2>
Continue?
The program expects you to insert volumes in sequential order. If a volume appears out of order, restore prints this message. If you type anything except an "n" or an "N" as the first character of the response to the message, restore ignores the fact that the volumes are out of order and continues with the backup. Otherwise, it prompts you for another volume. It is important to insert volumes sequentially because restore cannot correctly restore files that are broken across volumes if the volumes are inserted out of order.
Volume <number> of <vol name>
Whenever a new volume is inserted and properly validated, the program prints this message, which indicates the name of the backup volume and its sequence number.
ERROR MESSAGES
<dev name> is not a block device
The destination device for the backup must be a block device. This message indicates that the specified device (that is always the first argument) is not a block device.
<file_name> not located - try again?
When using the program in restore mode, you may specify which files or directories to restore. If the program cannot find a specified file or directory after searching the entire backup, it prints this message. If the response is not "n" or "N", the program searches the entire archive again.
This option is allowed because volumes need not be inserted in order of their creation when the program is in restore mode.
If one volume is left out or if the final volume is inserted before the entire archive has been processed, some files might not be processed. Note that if you specify more than one file name or directory name, the program processes the entire archive for each file before proceeding to the next one.
Formatting not allowed during Catalog/Restore You may not format a disk with the restore command.
Read error! - file <file name>
An error occurred during the transfer of a file either to or from the backup. An auxiliary message is printed indicating the nature of the error. The program tries to continue for all errors except device full during restore mode.
unknown option <char>
The option specified by <char> is not a valid option to the backup command.
**
Warning: directory <dir_name> is too large!**
Some directories were ignored**
Warning: directory <dir_name> is too large!**
Some files were ignoredThe program uses some internal tables during the backup process (not during restore or catalog).
If the limits of these tables are exceeded (highly unlikely), these messages are printed.
SEE ALSO
backup owner perms script shell
USER COMMANDS rmpath
rmpath
Changes the search path of the shell environment variable "PATH".
SYNTAX
rmpath <dir name list>
DESCRIPTION
Remove the specified directories from the search path of the shell. This is done by altering the shell environment variable "PATH".
ARGUMENTS
<dir name list> -
-
List of directory names to remove from the search path.EXAMPLE
rmpath lete
This example removes the directory "/etc" from the shell path, by removing the directory from the environment variable "PATH".
SEE ALSO
addpath set shell unset
script
Command interpreter.
SYNTAX
script [+abcnvx] [<argument_list>] [<script_filename>]
DESCRIPTION
The program named script is a command interpreter used primarily to execute commands from a file. It can be run as an interactive interface, but does not support aliases, interactive environment variables, or history, available under shell.
If you run script as an interactive shell, it collects and interprets your commands and executes some built-in commands (chd, dperm, jobs, log, login, time, and wait) itself. It passes others to the operating system kernel which, in tum, performs the operations requested.
A script command line consists of a command name, which may be followed by arguments, options, or both. All elements of the command line must be separated by either spaces or commas. The command may be one of the commands supplied with the operating system, the name of a binary file produced by either the assembler or a compiler, or the name of a text file (with execute permission turned on) which contains a series of commands to execute.
If the script command is executed without any options or arguments, the operating system simply spawns another shell for you. This script program functions as a normal shell, but because it is the child of the shell or script program from which the command was executed, it does not know what your home directory is. The log command terminates the child shell and returns control to the parent script.
The script command can also be executed with options only. This form of the command also spawns a script program that interacts with you.
Finally, the script command can be executed with arguments, or with both options and arguments. This form may be used, for example, to execute a script script for which you do not have execute permissions. The following command executes the file script Jilename:
script <script_filename>
script first checks to see that the file specified as an argument is actually a file that contains commands. If it is not, script executes it only if you specify the "c" option (see Options).
USER COMMANDS appropriate arguments and options. The elements in the list must be d b al·d d (" II "&" "&&"
"1Itt)
If separate y a v 1 cornman separator ;, , , or . any separator characters are used, the entire argument list must be enclosed in single or double quotation marks.The name of a file containing commands to execute.
Options specified to the script program must appear immediately after the name script on the command line, so that they are not confused with options that pertain to the arguments passed to the script.
Start execution with the sabort attribute off.
Ignore CTRL-C and CTRL-\.
Process the argument list as a command.
Run all background jobs with lower priority, i.e., "nice".
Start execution with the verbose attribute on.
On the next command, do not fork unless necessary. This option is used only when calling a script program from another program.
NOTE
It is impossible to specify a null string as an argument to a command because the script program removes null strings from the command line.