Recursive on Michael’s Domain

Copying with rsync

Mon, 17 Feb 2020 00:00:00 +0000

Reasons why you should (not always, but often) prefer rsync over cp:

Resume Interrupted Transfers If you are copying a large file and your terminal session crashes or the power cuts out, cp will simply fail, and you have to start over. rsync can pick up right where it left off, which is a massive time-saver for large datasets.
Efficiency (Delta-Transfer Algorithm) rsync is designed to be smart. If you are copying a file that already exists at the destination (e.g., you are updating a backup), rsync only copies the parts of the file that have actually changed (the “delta”) rather than overwriting the entire file. cp, by contrast, always copies the whole file every single time.
Real-time Progress Monitoring rsync provides excellent visual feedback. By using the -P (or –progress) flag, you get a real-time progress bar showing the percentage complete, transfer speed, and estimated time remaining. cp is famously silent, leaving you guessing whether the process is still running or has hung, requiring you to check at the destination via the size of the arriving file, whether anything is progressing (ls -lh filename, or du -hs filename)
Seamless Remote Transfers rsync is natively built to work over SSH. You can use it to copy files directly to or from a remote server as easily as copying files on your local machine. cp cannot do this; to use cp for a remote server, you would first need to mount the remote filesystem locally, which is far more complex and prone to errors.

Here is a common use case, the transfer of a directory, including all of its content:

Linux copy (cp)

Wed, 17 Apr 2019 00:00:00 +0000

In order to copy all xml files from one directory to another without overwriting existing files with the same name:cp -vnpr /source/*.xml /destination

File permissions on html server (recursive chmod) differentiating between files and directories

Sun, 12 Apr 2009 00:00:00 +0000

I recursively screwed up the file permissions in my html servers root directory. To fix it I needed to deploy some “advanced” chmod settings. Obviously I want to treat directories and files differently. I didn’t come up with a better solution than the following:chmod -R u=rw-x,g=rw-x,o=r-wx *chmod -R a+X *

Recursive grep

Thu, 05 Apr 2007 00:00:00 +0000

grep (case-insensitive, recursive) grep doesn’t offer any possibility to recursively descent down the directory tree. The following command searches e.g. just thru all the files in the current directory:grep bacteria *To make the search case-insensitive, one can use the i flag:grep -i bacteria *But if you want to do a recursive search you have to use a quite complicated construction of UNIX commands to achieve this goal:find ~/Mail -type f -exec grep 'bacteria' {} \; -printThis command searches recursively thru the Mail directory of the current user and prints all the lines that contain the word bacteria.

Find and replace with perl

Sun, 28 Jan 2007 00:00:00 +0000

To replace the string jeltsch.blogspot.com by the string mnm.no-ip.com/blog you can use perl:perl -pi.bak -e 's|jeltsch.blogspot.com|mnm.no-ip.com\/blog|g' *.html If you want to do a recursive replacement on a directory tree you can try:perl -pi.bak -e 's|jeltsch.blogspot.com|mnm.no-ip.com\/blog|g' find jeltsch.org -name ‘*.html’``