3 private links
For the TL;DR crowd: I desperately needed to extract the complete (and very lengthy) command line I had written 6 months ago in a bash shell - which was still running under screen. Read on to see how I eventually made it...
Use an HSM for SSH Keys
After a lot of trial and error, we narrowed it down to this:
EXEC 00
SETUID 00
SETGID 00
CAPABILITY 00
which translates in
export LS_COLORS='ex=00:su=00:sg=00:ca=00:'
waterhouse 2 days ago | parent [-] | on: I got tired of PHP and Perl, so I tried bash
$ cat meh.bash
!/bin/bash
set -e
die() {
echo "Failed at line $1: $2"
}
trap 'die $LINENO "$BASH_COMMAND"' ERR
echo a
test 1 = 3
echo b
$ ./meh.bash
a
Failed at line 8: test 1 = 3
Adapted from: https://unix.stackexchange.com/a/462157
BashFAQ/105 - Greg's Wiki
set -e was an attempt to add "automatic error detection" to the shell. Its goal was to cause the shell to abort any time an error occurred, so you don't have to put || exit 1 after each important command.
Scripting with Postgres
Sometimes bash is just the way to go! This talk will cover tips and techniques for effective bash scripting with PostgreSQL.
Sometimes bash is just the way to go! This talk will cover tips and techniques for effective bash scripting with PostgreSQL.
It will include guidance about:
Pros/cons of shell scripts
Function library creation and use
Executing SQL
Set/get PostgreSQL data from/into script variables
Keeping PostgreSQL functions in sync with scripts
Locking
Doing work in parallel
Ensuring cleanup
This is a source-code heavy talk. Moderate experience with both bash scripting and PostgreSQL is needed to get the most out of it.