RSS Feed for sh - James Stone's Blog

Find sqlite dbs

Mon, 25 Nov 2024 00:00:00 GMT

Lots of applications use sqlite dbs. It can be useful to try and find them all. For this you can use the following command

find . -type f -exec sh -c 'head -c 16 "$1" 2>/dev/null | grep -q "^SQLite format" && echo "$1"' _ {} \;

as all sqlite files start with the header string: “SQLite format 3\000” , see: Database File Format

it can then be helpful to get the size of each result

find . -type f -exec sh -c 'head -c 16 "$1" 2>/dev/null | grep -q "^SQLite format" && echo "$1 $(stat -c%s "$1" | numfmt --to=iec)"' _ {} \;

]]>

Adding auto complete in bash

Thu, 29 Aug 2024 00:00:00 GMT

in bash code completions are setup using the complete command

you can print all current system completion s using complete -p

]]>

Interactively debug a sh script

Wed, 16 Aug 2023 00:00:00 GMT

My common (ba)sh script setup is a bit like this:

# By default, in a pipeline of commands, the exit status of the pipeline is determined by
# the exit status of the last command in the pipeline. This changes that to fail if any command fails
set -o pipefail

# stop on exit
set -o errexit

# trace , print all commands before running.
set -x

Another approach that I just thought of that is useful is to enter an interactive shell should a command fail. eg


may_fail || bash

This is particularly useful when in a loop and subshell:


find "$root_directory" -type d | while read -r dir; do
    {
      cd "$dir"
      may_fail || bash # explore current state if this fails.
    }
done

It allows the loop to pause until you’re ready to continue by pressing Ctrl + d, or you can exit entirely using Ctrl + c.

]]>