Commands tagged bash

uses fifo and sets to a specific port. In this case 4201.

Find all files in /var/spool/mqueue older than 7 days, pass to perl to efficiently delete them (faster than xargs or -exec when you've got millions or hundreds of thousands to delete). Naturally the type, directory, and file age vars can be adjusted to meet your specific needs.

Change "sort -f" to "sort" and "uniq -ic" to "uniq -c" to make it case sensitive.

Type out the command and simply press to see the list of options for that command without having to type --help.

You can find a command's history event number via the `history` command.

You can also put the history event number in your prompt: \! for bash, or %h for zsh.

Finally, I would like to point out that by "number", I mean POSITIVE INTEGER. Not, say, a letter, such as 'm'. Examples:

or

Dock Thunderbird in system tray and hide main window. Very useful for startup scripts.

Of course you can dock any app of your choice.

The biggest advantage of this over the functions is that it is portable.

Outputs the real time it takes a Redis ping to run in thousands of a second without any proceeding 0's. Useful for logging or scripted action.

nothing special

Normally, if you just want to see directories you'd use brianmuckian's command 'ls -d *\', but I ran into problems trying to use that command in my script because there are often multiple directories per line. If you need to script something with directories and want to guarantee that there is only one entry per line, this is the fastest way i know

quoteless

No command substitution but subshell redirection

Pi also says hello world!

This version uses read instead of eval.

It's quite easy to capture the output of a command and assign it in a shell's variable:

But, what if we want to perform the same task with just one program invocation? Here comes the power of eval! date(1) outputs a string like "day=29; month=07; year=11" (notice the semicolons I added on purpose at date's custom output) which is a legal shell line. This like is then parsed and executed by the shell once again with the help of eval. Just setting 3 variables!

Inspired by LinuxJournal's column "Dave Taylor's Work the Shell".

In addition to generating the current connections, it also opens then in your default browser on gnome.

Use this to find identify if dirs mostly contain large or small files.

no need for seq or eval

In order to create, let's say, 10 directories with a single process we can use the command:

something extremely boring to type! Why not use seq?

and use its output inside the curly braces?

The obvious solution

is, unfortunately, too naive and doesn't work. The answer is the order of the shell expansions (feature of Bourne Shell, actually), where brace expansion happens before command substitution (according to Bash's manual).

The solution is to put another level of substitution, using the powerful and mystic command eval.

I found the trick in a similar problem in the post at http://stackoverflow.com/questions/6549037/bash-brace-expansion-in-scripts-not-working-due-to-unwanted-escaping