Centrify Express is a comprehensive suite of free Active Directory-based integration solutions for authentication, single sign-on, remote access, file-sharing, monitoring and cloud security for cross-platform systems. It is the quickest and most proven solution for integrating UNIX, Linux and Mac systems with Windows, and delivers more functionality and more to upgrade to when compared to other free offerings.

 750 total views

There seem to be two that would work for you.

See my own(Seth Leedy’s) script for downloading GRC Security Now Podcasts!

A Windows script, and a BASH script which could be run on both Windows or L/Unix.
wget for windows, here.
BASH for Windows, here.

Copied from the g.securitynow newsgroup hosted on on date 2012-05-12 07:51 AM.
First message. Subject: “Little SN download script”

Hi all,

I wanted to download every episode of Security Now so I could go back and
listen to the back-catalogue (I've only been listening for a few months).

I threw together a little bash script to pull down all the episodes from I'm posting it here in case anyone else wants to use it (you
need wget):

As it states, he was publishing a script to download all Security Now episodes from the server.
This spawned a few messages of how to do it differently.
I am attempting to record all these different ways for future downloaders.
If you attempt this, set aside some space. As of 2012-05-16, approx: 11.8GB for HQ, 3.62GB for LQ.

James Womack:

echo "Download episodes $1 to $2:"
for ((ii=$1;ii<=$2;ii++))
printf -v number "%03d" $ii
echo "Episode: $number"

Hi James,

I also make use of scripting to maintain my SN-archive. Attached you will find the ones I made. Their function is very simple and as a default (void of argument) will “guesstimate”, i.e. make use of previously downloaded stuff and then based upon that derive “next” episode for download.

Big note: As you, I wrote these in a bit of a haste a few years back and I had absolutely no intention of the code being scrutinized by this community or anyone else for that matter. If you find the code yucky, or beyond, most likely I am already agreeing. If you see solutions in the code that could have been written a lot more clever, again it comes as no surprise at all.

Disclaimer: These scripts are not guaranteed to be failsafe, foolproof or even to work…but to my experience they usually do, at least in line with my initial description. These scripts are definitely not compatible with the intentions of the RIAA, MPAA or any other racketeering organization affiliated with Sony and the other legitimate crooks of our time and society. Then again, anything able to download whatever or for that matter technology in general beyond the abacus is probably incompatible along those lines…


# Initialization.
declare -i DISK_SPACE
declare -i DISK_SPACE_MIN="5000000"
declare -i EPISODE

# Output title.
echo "Security Now Downloader v0.7 (GRC)"

# Check disk space.
DISK_SPACE=$(df -T /data/disk1/ | grep disk1 | awk '{print $5}')
if [ "$DISK_SPACE" -le "$DISK_SPACE_MIN" ]; then
echo "Minimum amount of diskspace not available! Exiting."
exit 1

# Check argument and set episode.
if test "$1"; then
echo "Episode input: ${EPISODE}"
#EPISODE=$(ls -1 ./Audio/*.mp3 | tail -n 1 | grep -io "^sn-..." | grep -o "...$")
EPISODE=$(ls -1 ./Audio/*.mp3 | tail -n 1 | grep -io "[0-9][0-9][0-9]")
echo "Episode input missing, guesstimating: ${EPISODE}"

# Check length.
case "${#EPISODE}" in
1) EPISODE="00${EPISODE}" ;;

# Set episode filename and download.
echo "Downloading episode ${EPISODE}..."
echo " ${NETCAST_URL}"
wget -P ./Audio/ "$NETCAST_URL"
echo " (LQ) ${NETCAST_LQ_URL}"
wget -P ./Audio/ "$NETCAST_LQ_URL"
echo "...transcript ${NETCAST_TRANSCRIPT_URL}"
wget -P ./Transcripts/ "$NETCAST_TRANSCRIPT_URL"
echo "...done."

exit 0


# Initialization.
declare -i DISK_SPACE
declare -i DISK_SPACE_MIN="200000"
declare -i EPISODE

# Output title.
echo "Security Now Downloader v0.8"

# Check disk space.
DISK_SPACE=$(df -T /data/disk1/ | grep disk1 | awk '{print $5}')
if [ "$DISK_SPACE" -le "$DISK_SPACE_MIN" ]; then
echo "Minimum amount of diskspace not available! Exiting."
exit 1

# Check argument and set episode.
if test "$1"; then
echo "Episode input: ${EPISODE}"
EPISODE=$(ls -1 *.mp4 | tail -n 1 | grep -io "^sn0..." | grep -o "...$")
echo "Episode input missing, guesstimating: ${EPISODE}"

# Set episode filename and download.
echo "Downloading episode ${EPISODE}..."

echo "...done."

exit 0

Now gdb says to use this


and it spawned a large response thread.

Guy says:
Thanks for the information.
I use Windows – so curl is the tool for the task of topic.

curl -OL[001-352].mp3

Mark Cross adds:
Adding -N check timestamp and wont download existing files (if they haven’t changed) and -c to continue existing downloads:
echo wget -Nc${padding:${#i}}$i.mp3

A real ‘one liner bash command’ needs some artistic tweaking (for bash 3.1):
a=’printf %03d’ eval “wget -Nc{$($a 1)..$($a 25)}.mp3”

or (won’t mess with the environment vars set on present shell, for bash 3.1):
sh $(beg=1;end=25;a=’printf %03d’;eval “wget -Nc{$($a $beg)..$($a $end)}.mp3”)

and (for bash 4):
sh $(beg=001;end=025;eval “wget -Nc{$beg..$end}.mp3”)

maybe a bit too complex ;)

ObiWan says something interesting for Windows:

Well... if you're running windows, then you may also leverage the BITS
tool (Background Intelligent Transfer System); the critter integrates
with the windows network stack and ensures that ongoing downloads won't
clogger your bandwidth; this means that BITS won't be the faster way to
download stuff but it will, for sure, be the less "impacting" one; you
probably won't even notice that it's fetching stuff

The cornerstone of such a thing would be a tool called "bitsadmin"

basically it's a cmdline interface to the BITS service; as for every
windows app/service, there are several ways to use it; the most simple
and straightforward one is the following

bitsadmin /transfer JOBX /download /priority normal d:\SN\sn-001.mp3

the above (single line) will create a job called JOBX, add it a file,
that is "sn-001.mp3", tell it to download the file to d:\SN and then,
immediately start the job in sync mode (just like entering "wget..."
from the cmdline) then... ok, there are other ways to use it; for
example, you may create background jobs which will run (and fetch the
desired files) and which, at end (ok or error) will call whatever
script/program or piece of code you want

The BITS subsystem is the one used by windowsupdate to fetch files and
while it isn't "fast" (not its purpose) I think it's worth exploring

ObiWan also came up with this and I think, right now anyways, this would be the best way to do it for Windows users:

The below will fetch all the episode from 001 to 100 (for…) and save
then in c:\sn the episode number is correctly aligned with zeroes by
that “%NBR:~-3%”; basically the code first adds 000 in front of the
number and then picks the rightmost 3 chars

@echo off
if not (%1)==() goto FETCH
for /L %%n IN (1,1,100) DO call %0 %%n
goto QUIT
set NBR=000%1
set NBR=%NBR:~-3%
bitsadmin /transfer J%RANDOM% /download /priority normal c:\sn\sn-%NBR%.mp3

 11,468 total views

From: What does “> /dev/null 2>&1″ mean? at Xaprb.

I remember being confused for a very long time about the trailing garbage in commands I saw in Unix systems, especially while watching compilers do their work. Nobody I asked could tell me what the funny greater-thans, ampersands and numbers after the commands meant, and search engines never turned up anything but examples of it being used without explanation. In this article I’ll explain those weird commands.

Here’s an example command:

wibble > /dev/null 2>&1

Output redirection

The greater-thans (


) in commands like these redirect the program’s output somewhere. In this case, something is being redirected into


, and something is being redirected into



Standard in, out, and error

There are three standard sources of input and output for a program. Standard input usually comes from the keyboard if it’s an interactive program, or from another program if it’s processing the other program’s output. The program usually prints to standard output, and sometimes prints to standard error. These three file descriptors (you can think of them as “data pipes”) are often called STDIN, STDOUT, and STDERR.

Sometimes they’re not named, they’re numbered! The built-in numberings for them are 0, 1, and 2, in that order. By default, if you don’t name or number one explicitly, you’re talking about STDOUT.

Given that context, you can see the command above is redirecting standard output into


, which is a place you can dump anything you don’t want (often called the bit-bucket), then redirecting standard error into standard output (you have to put an


in front of the destination when you do this).

The short explanation, therefore, is “all output from this command should be shoved into a black hole.” That’s one good way to make a program be really quiet!

 709 total views