New Application: S. N. A. P.

BRiT · January 21, 2011

~ stands for the home directory. for the user root it is /root

so, if you type "cd /root" or "cd ~" you get to the same directory

Ah, thanks. So then what I still don't quite understand is if I'm in the root directory (root@Tower:~#) and I type cd.. I get the command prompt root@Tower:/# this is the same thing as root@Tower:~# because you can't go up any directories past the root level?

No. They are different, "/" is not the same as "/root". If you are logged in as root, then "~" is the same as "/root". So, "/" is not "/root".

You were in "/root" (which is the same as "~" for user 'root'), then did a "cd ..", so you're then in "/".

The "/" is the root filesystem.

The "/root" is the home directory for user 'root'.

Most unix shells allow for "~" to be an abbreviation for the home directory for the current user.

Do not confuse root filesystem for root home directory.

BlackCat · January 21, 2011

~ stands for the home directory. for the user root it is /root

so, if you type "cd /root" or "cd ~" you get to the same directory

Ah, thanks. So then what I still don't quite understand is if I'm in the root directory (root@Tower:~#) and I type cd.. I get the command prompt root@Tower:/# this is the same thing as root@Tower:~# because you can't go up any directories past the root level?

No. They are different, "/" is not the same as "/root". If you are logged in as root, then "~" is the same as "/root". So, "/" is not "/root".

You were in "/root" (which is the same as "~" for user 'root'), then did a "cd ..", so you're then in "/".

The "/" is the root filesystem.

The "/root" is the home directory for user 'root'.

Most unix shells allow for "~" to be an abbreviation for the home directory for the current user.

Do not confuse root filesystem for root home directory.

Ok that helps to explain things. Thanks for the clarification.

queeg · January 22, 2011

I'm about to release a new version 0.47 of SNAP. I need a beta tester if anyone would volunteer it would be very helpful.

I've automated the installation and that is what needs testing mostly. Attached to this posting is a zip file with two scripts that need to be placed into the /boot/unmenu folder. They will add two new buttons on the unmenu User Script page.

Check for SNAP Updates

Install SNAP uPDATES

The Check button downloads a tarball from google.code of SNAP 0.47 beta which gets extracted to /tmp/snap folder. Included is snap-install.sh.

After the Check button download, the Install button will appear (I had to do an F5 refresh on the page to get it to appear).

The Install button runs the /tmp/snap/snap-install.sh. It may take a system restart before all parts will be writing to the new log location - I'm just not certain.

UPDATE:

If SNAP is already installed, all /boot/config/snap files will be backed up to a folder with a name like /boot/config/snap/save_Jan21-2011-023305. Then /tmp/snap/snap.sh is copied in and some editing is done to the other .sh files to modify where the log file entries are sent. Log files are now being moved to /var/log/snap folder. No data files are touched.

FRESH INSTALL:

If SNAP not installed then all files /tmp/snap are copied to /boot/config/snap and snap.sh -install is run. Adding drives to SNAP is still a manual process.

### v 0.47 changes: 1/21/2011

### Added: -v parameter

### Added: support for hfsplus filesystem.

### Changed: samba restart method to kill -1 method.

### Changed: samba user: "nobody" now check if exists, created only if doesn't.

### Changed: moved all logs to /var/log/snap directory

### Corrected: -M usage description.

### Corrected: snapEventss.log to snapEvents.log

snap_user_script_buttons.zip

Joe L. · January 22, 2011

I'm about to release a new version 0.47 of SNAP. I need a beta tester if anyone would volunteer it would be very helpful.

I downloaded the two scripts to my server.

GOing to the User-Scripts page showed just the "Check" button, as expected.

Pressing it showed the following on the bottom of the screen.

--2011-01-22 08:51:40-- http://unraid-snap.googlecode.com/files/snap-0.47-beta2.tgz Resolving unraid-snap.googlecode.com... 74.125.67.82 Connecting to unraid-snap.googlecode.com|74.125.67.82|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 100403 (98K) [application/x-gzip] Saving to: `/tmp/snap/snap-0.47-beta2.tgz' 0K .......... .......... .......... .......... .......... 50% 505K 0s 50K .......... .......... .......... .......... ........ 100% 40.4K=1.3s 2011-01-22 08:51:42 (76.0 KB/s) - `/tmp/snap/snap-0.47-beta2.tgz' saved [100403/100403] A file was downloaded: snap-0.47-beta2.tgz ; hotPlugAfterShareEvent.sh ; inotify-tools-3.8-i486-1.tgz ; snap-0.47-beta2.tgz ; snap-global-template ; snap-install.sh ; snap-xdrive-template ; snap.sh ; snapCommon.sh ; snapEvents.sh ; snapNotify.sh ; snapSambaNotify.sh

There is no "Install" button showing. I think the display of what will be downloaded needs some formatting..

If I were to "refresh" the screen it would perform the download again. You probably could use use the same type of technique I used for the Check for Updates button of unMENU itself and render your own "Install Updates" button in the returned text as I did in the unMENU "Check for Updates" button. It will make it so you do not have to leave the page and return to it to perform the "install"

I did that by putting the list of files in variable "$f" and rendering it after the "<pre>" tag. I rendered an "Install" button if updates existed.

I clicked on the "About" link, and then clicked on the "User-Scripts" button to go back, and then the "Install" button appeared, but most users will not know to do that.

The lines you are not properly using are the last two in the button scripts.

echo "<pre>"

echo "$f"

The $f variable needs to have whatever you want neatly rendered, or you need to render HTML.

All in all, a very nice start.

Joe L.

queeg · January 22, 2011

I'm about to release a new version 0.47 of SNAP. I need a beta tester if anyone would volunteer it would be very helpful.

I downloaded the two scripts to my server.

GOing to the User-Scripts page showed just the "Check" button, as expected.

Pressing it showed the following on the bottom of the screen.

--2011-01-22 08:51:40-- http://unraid-snap.googlecode.com/files/snap-0.47-beta2.tgz Resolving unraid-snap.googlecode.com... 74.125.67.82 Connecting to unraid-snap.googlecode.com|74.125.67.82|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 100403 (98K) [application/x-gzip] Saving to: `/tmp/snap/snap-0.47-beta2.tgz' 0K .......... .......... .......... .......... .......... 50% 505K 0s 50K .......... .......... .......... .......... ........ 100% 40.4K=1.3s 2011-01-22 08:51:42 (76.0 KB/s) - `/tmp/snap/snap-0.47-beta2.tgz' saved [100403/100403] A file was downloaded: snap-0.47-beta2.tgz ; hotPlugAfterShareEvent.sh ; inotify-tools-3.8-i486-1.tgz ; snap-0.47-beta2.tgz ; snap-global-template ; snap-install.sh ; snap-xdrive-template ; snap.sh ; snapCommon.sh ; snapEvents.sh ; snapNotify.sh ; snapSambaNotify.sh

There is no "Install" button showing. I think the display of what will be downloaded needs some formatting..

If I were to "refresh" the screen it would perform the download again. You probably could use use the same type of technique I used for the Check for Updates button of unMENU itself and render your own "Install Updates" button in the returned text as I did in the unMENU "Check for Updates" button. It will make it so you do not have to leave the page and return to it to perform the "install"

I did that by putting the list of files in variable "$f" and rendering it after the "<pre>" tag. I rendered an "Install" button if updates existed.

I clicked on the "About" link, and then clicked on the "User-Scripts" button to go back, and then the "Install" button appeared, but most users will not know to do that.

The lines you are not properly using are the last two in the button scripts.

echo "<pre>"

echo "$f"

The $f variable needs to have whatever you want neatly rendered, or you need to render HTML.

All in all, a very nice start.

Joe L.

I tried putting in newlines but that didn't work. I suppose it needs html formatting. I don't think it downloads twice. But in any case it takes the page refresh to get it to show the second button. I looked at your button and couldn't figure out how it worked.

Joe L. · January 22, 2011

I'll try to explain

First, I collect whatever file list and stuff I want to print in the results in a single variable

You can probably do something like this with your main logic. Surrounding it with parens "()" and capturing the output in $f

f=`(
   echo this is the contents of /tmp
   ls /tmp
   ls /tmp | while read a
   do
     if [ -d "$a" ]
     then
       echo "Found directory $a"
     fi
   done
   # do whatever you need to create your list of files to download, as you currently are.
   )`

echo "<pre>"
echo "$f"

If you put your list of files in /tmp in a specific file (as you already are), and test for its existence prior to rendering a "Install SNAP Updates" button in the resulting HTML it will work like unMENU's install button.

It will then look like this:

f=`(
   # do whatever you need to create the /tmp/snap.newfiles list of files to be installed, as you currently are.
   echo "Checking for updates"
   # your wget and md5 check loop goes here.
    )`

echo "<pre>"
if [ -f /tmp/snap.newfiles ]
then
cat <<EOF
<form target="user_scripts">
<input type=submit name="command" value="Install SNAP Updates"> Download and install SNAP Updates.<br>
</form>
EOF
fi
echo "$f"

The "cat <<EOF" will copy the enclosed text until it gets to the matching "EOF" This is called a "here document" in the shell.

The content is the HTML for a form with a submit button. The target is the user_scripts page where you have a matching "Install SNAP Updates" user-script to invoke.

You are so close...

Joe L.

BlackCat · January 22, 2011

Well I did run: root@Tower:/boot/config/snap# snap.sh -listDeviceConfiguration

BUT I see I forgot to add the next command line prompt.

After entering snap.sh -listDeviceConfiguration in the correct location

I am returned to the root@Tower:/boot/config/snap# prompt without seeing any device list.

I have attached my snapNotify and snapSambaNotify they both say, Error occured - inotify not installed

Would this be because I did not unzip the inotify-tools-3.8-i486-1.tgz file?

Hopefully that helps with the understanding of my problem, not that I'm understanding some basics.

I still need some help with this since it looks like my inotify tools didn't install. Should I run the uninstall command and then try to install SNAP again? Do I unzip the inotify-tools-3.8-i486-1.tgz file before running the install command? Can I install the missing items without uninstalling SNAP? I read through the thread all over again, but I didn't see (maybe i missed something) that shed some light on this.

queeg · January 23, 2011

Well I did run: root@Tower:/boot/config/snap# snap.sh -listDeviceConfiguration

BUT I see I forgot to add the next command line prompt.

After entering snap.sh -listDeviceConfiguration in the correct location

I am returned to the root@Tower:/boot/config/snap# prompt without seeing any device list.

I have attached my snapNotify and snapSambaNotify they both say, Error occured - inotify not installed

Would this be because I did not unzip the inotify-tools-3.8-i486-1.tgz file?

Hopefully that helps with the understanding of my problem, not that I'm understanding some basics.

I still need some help with this since it looks like my inotify tools didn't install. Should I run the uninstall command and then try to install SNAP again? Do I unzip the inotify-tools-3.8-i486-1.tgz file before running the install command? Can I install the missing items without uninstalling SNAP? I read through the thread all over again, but I didn't see (maybe i missed something) that shed some light on this.

Hang in there. inotify package gets copied to the /boot/packages folder when snap.sh -install is run, and also /boot/config/snap/snap.sh -b is added to the /boot/config/go file. When the system is started up the /boot/config/go file is run and when that happens snapNotify.sh is started. snapNotify.sh will install the inotify package if it's not already installed.

So, if you have not rebooted your machine then it's possible that /boot/config/snap/snap.sh -b hasn't been run yet. You can run that manually this time if you want. Then check if SNAP is running.

dwoods99 · January 23, 2011

Not much trouble getting this installed and in use -- thanks.

One question, is it possible to share the parent folder /mnt/disk instead of each individual HDD mounted within it?

I would prefer to only create 1 mount point for all the HDDs internally which are not part of unRAID.

BlackCat · January 23, 2011

Hang in there. inotify package gets copied to the /boot/packages folder when snap.sh -install is run, and also /boot/config/snap/snap.sh -b is added to the /boot/config/go file. When the system is started up the /boot/config/go file is run and when that happens snapNotify.sh is started. snapNotify.sh will install the inotify package if it's not already installed.

So, if you have not rebooted your machine then it's possible that /boot/config/snap/snap.sh -b hasn't been run yet. You can run that manually this time if you want. Then check if SNAP is running.

Ok, so I rebooted again this morning. I'm not sure why it was any different this time than the last since I had rebooted after I installed the first time. Any at the end of the boot I am seeing:

cat: /boot/config/snap/snap.list: No such file or directory

/boot/config/snap/snap.sh: All shares mounted

cat: /boot/config/snap/snap.list: No such file or directory

So I went ahead entered the snap.sh -listDeviceConfigurationInfo and I get the following:

Tower login: root

Linux 2.6.32.9-unRAID.

root@Tower:~# cd /boot/config/snap

root@Tower:/boot/config/snap# snap.sh -listDeviceConfigurationInfo