Thanks, read. X E.
|
I think I prefer on main drive, newer stuff should have bug fixes and like and yes, I know how to find it. Thanks. X E.
|
Like my main concern about using rsync is if I overwrite rsync, what happens to that running program with restore. With that reply I assume it would keep running fine. X E.
|
If you type in the command "rsync", the bash shell will search for a command named "rsync" within the current $PATH. You can see the $PATH with this:
Code:
echo $PATH This is similar to how things work on, say, MS-DOS, but in Linux this $PATH will basically never include the current directory. The bottom line is that it will only execute the copy of rsync that's from the currently running OS, and never any other copy of rsync unless you for some (stupid) reason specify otherwise with a full path or relative path to some other copy of rsync. |
Quote:
In such cases, the operating system may continue to run the copy in RAM, as long as the system does not attempt to access the original file on disk. This can cause an instant crash (of that app). |
There is no danger with rsync. For example, if you have /usr/bin/rsync on disk and want to restore a different version from backup: rsync copies to file name /usr/bin/rsync.NKnduM (last six characters are random). Only when done copying, it renames it to /usr/bin/rsync. So, it doesn't use the old file's inode but creates a separate one. The running rsync process continues to use the old binary on disk and the old inode is removed from the disk only after the last user stops using it.
|
Quote:
But your command 'rsync -vrlDAXHxog' (mtime not preserved) will always start from the beginning and copy everything again after an interrupt. Quote:
|
Quote:
|
All times are GMT -5. The time now is 06:48 PM. |