Скачать или смотреть How to Fix the tar Command Failing in a Script

Learn how to troubleshoot and resolve issues with the `tar` command in scripts, focusing on solving common problems caused by line-ending formats.
---
This video is based on the question https://stackoverflow.com/q/64288608/ asked by the user 'Corbin' ( https://stackoverflow.com/u/7387924/ ) and on the answer https://stackoverflow.com/a/65266118/ provided by the user 'Corbin' ( https://stackoverflow.com/u/7387924/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: This tar command works on command line but fails in a script

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Fix the tar Command Failing in a Script: A Step-by-Step Guide

If you’ve ever run a command in the terminal that worked perfectly, only to have it fail when you include it in a script, you're not alone. Many users encounter frustrating issues when moving commands from the command line to shell scripts. One common issue arises when using the tar command, as illustrated in the question that follows.

The Problem

In this case, the command was successful in the command line interface but failed when executed within a script. The command used is:

[[See Video to Reveal this Text or Code Snippet]]

Expected Output

When run directly in the terminal, the command produces a nice archive of .db files without any issues:

[[See Video to Reveal this Text or Code Snippet]]

The Error

However, when included in a shell script (named backup.sh), the user encountered the following error:

[[See Video to Reveal this Text or Code Snippet]]

This may leave many scratching their heads wondering what went wrong.

Diagnosis

The root of the issue often lies in the line-ending format used in the script. The command line can handle both Unix and Windows line endings, but scripts are particular. Here, the script likely had Windows-style line endings (CRLF), leading to the unexpected -\r being interpreted by tar.

Solution: Converting Line Endings

To resolve this issue, you can convert the file's line endings to the appropriate Unix format (LF). Below are the steps you can take to fix it:

Use a text editor: A simple solution is using a text editor that allows you to change the EOL (end of line) characters.

Recommended Tool: Notepad+ + , a lightweight code editor, can be used for this purpose.

Steps to convert line endings:

Open the script file backup.sh in Notepad+ + .

Navigate to Edit EOL Conversion.

Select UNIX (LF).

Save the file.

Revised Script Code: After converting the line endings, your script should look something like this:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

Running into a situation where commands work in the terminal but not in scripts can be confusing and frustrating. Understanding that line endings play a significant role in script execution is key. Remember to always check your line endings if you find yourself facing similar issues in the future.

By converting your script's line endings to the Unix format, you should be able to run your tar command successfully in scripts without any further hiccups. Happy scripting!