purko

Why don't you simply tell rtorrent to put the completed stuff in that "somewhere else"? If you really need to do some scripting, look into inotify. Inotify can send a message when the dir tree is modified in some way. The inotify-tools package provides a lightweight wrapper around the inotify api that is designed to be used in scripting. The man page for inotify is here: http://linux.die.net/man/7/inotify The Slackware install package can be obtained from here: ftp://slackware.osuosl.org/pub/slackware/slackware-current/slackware/a/ (The current version as of this writing is inotify-tools-3.14-i486-1.txz ) Google the web for plenty of examples of bash scripts using inotify. One such example: http://ubuntuforums.org/showthread.php?t=950939

but then...

But doesn't that also mean that those disk will slow you down for the second half of the parity calculation if you start them from there?

In that statement, you are giving us a nice solid number, without any qualifiers like around, or about, which implies that your number is very accurate. Knowing that 48.6 percent of all statistics are made up on the spot, I almost stopped reading right there. Other than that, the idea of staggering all smaller drives along the size of the big parity drive may turn out to be very interesting.

Zenwalk is a derived from Slackware, just like unRAID is. We can get the pm-utils from the Slackware distribution: ftp://slackware.osuosl.org/pub/slackware/slackware-current/slackware/ap/pm-utils-1.2.6.1-i486-1.txz

Why do you need to change directory, and then run the command? Can't you just run it with a fully qualified path? nohup /boot/custom/s3.sh &

It's funny how it estimates its remaining lifetime to be 4 days. Call us back in four days, will you?

I'm far from the best person to answer this, that's why I was looking for an article in the wiki on scripting issues that I thought I remembered reading before answering. But I couldn't find it It's here: http://lime-technology.com/wiki/index.php?title=FAQ#Why_do_my_scripts_have_problems_with_end-of-lines.3F

I only said thirty minutes for the sake of argument. My thinking was, if thre's been NO network activity in the past N minutes, and if all disks are asleep, then it is ok for the server to go to sleep.

There either was some network activity in the past 30 minutes, or there was no network activity in the past 30 minutes. These are the only two things you care about, aren't they?

I think that in this case here we don't really care to grep and cut stuff. Just take the whole thing and compare it with the later snapshot.

I think that we don't really need bwm-ng to determine if there has been some network activity. An simpler way would be to just read /proc/net/dev and assign it to a variable: NetSnapshot=$(cat /proc/net/dev) Then some time later you just take a new snapshot the same way, and compare the two. If $NetSnapshot = $NetNewSnapshot then no network activity had occured in between. Purko

That is corret. My media frontend (SageTV) also reads the cover images of all my videos. So the caching script that I am using copies all .jpg files it finds to /dev/null Purko

On that experimental box I was talking about, yes, you guessed it right. My main server is a six drives unraid, off of a flash key with registration.

Start a new thread for this please. I'm very interested. It's one of my pet peeves with unRAID. Nothing to it, really. Just prepare the hard disk as you would prepare a flash key, and label it UNRAID. Works the same.