11–14 of 14 posts
Earlier quoted context omitted.
It appends the "new" history lines to a $HISTFILE by default, unless other file is specified.
Thanks, that's what I was missing: -a can have a file. Cool stuff and thanks to all for explaining it. http://unixhelp.ed.ac.uk/CGI/man-cgi?history does not mention the command line argument, http://linux.die.net/man/1/bash does.
Unfortunately, it does not log the output of the command. For those that need to log absolutely everything, check out:
https://github.com/jpschewe/rootsh
rootsh is a wrapper shell for bash and logs everything.
What does history -a do? Seems to write the history to disc and not produce something to pipe into logger. How does this work?
With bash putting a command in I've never used it, but I assume >() uses a command as though it were a writable file. So instead of history -a file writing to file, he does history -a >(logger) to write to the logger command. Seems pretty clever to me.
$ cat writer.sh
#!/bin/bash
if [[ "$#" == 1 ]]; then
echo "Wrote to file named $1" > "$1"
else
echo "Wrote to stdout"
fi
$ ./writer.sh
Wrote to stdout
$ ./writer.sh | cat
Wrote to stdout
$ ./writer.sh >(cat)
Wrote to file named /dev/fd/63Interesting, but is there anything that can easily process syslog on the other end? ie. split data like this out into something useful?