WARNING: If your data dir is set to /mnt/cache/.Apps/ then WW's version will overwrite your settings on reboot.

 

..Now to set it back up

 

Its not a huge deal, I didn't lose anything that can't be fixed, but why did you hard code the install directories to the cache drive instead of /usr/local/ like it was?

 

EDIT: I merged the changes you made into my plugin, not sure if I'm the only one with a capital "A" in the directory path, but just in case, this will stop that from happening to someone else.

 

You can get it here

Its not a huge deal, I didn't lose anything that can't be fixed, but why did you hard code the install directories to the cache drive instead of /usr/local/ like it was?

 

The reason why i change the install directory to cache drive  (i have SSD cache drive) is that i want to have more space in RAM for directory caching and sabnzdb/sickbeard/couchpotato article caching. Another thing is that there is no need to always "build" sabnzdb/sickbeard/couchpotato directories when unraid starts - this is why i add version control so user can do install yourself.

I understand, the question was more in frustration, I was tired(LOOONG day) and had to redo my configuration.

 

That being said, if the user doesn't have a cache drive, it will be put into ram anyway, I'd think it best to give the user the option at the start, plugins install to ram, if the user wants it installed to disk, change the installdir to reflect this. But do how you see fit,

That being said, if the user doesn't have a cache drive, it will be put into ram anyway, I'd think it best to give the user the option at the start, plugins install to ram, if the user wants it installed to disk, change the installdir to reflect this. But do how you see fit,

 

Yes, you have right. But users should know that for example CouchPotato putting movie covers and fanart into datadir and for me, after few days i have over 100MB RAM used by CouchPotato images only.

Sabzndb+CouchPotato+Sickbeard installdirs and datadirs using for now 215MB RAM in my unRAID.

My PLex Media Server with only one category of couple movies using 723MB RAM.

if you want to take someone elses plugin and modify and re-release it - it would be prudent to start your own threat instead of muck up this thread.....

 

this thread is about sabnzdb and not couchpotato.....

 

also - not everyone has a cache drive, so a default to a cache drive is going to mess them up vs putting it into the RAM location......

 

Myk

 

if you want to take someone elses plugin and modify and re-release it - it would be prudent to start your own threat instead of muck up this thread.....

 

this thread is about sabnzdb and not couchpotato.....

 

also - not everyone has a cache drive, so a default to a cache drive is going to mess them up vs putting it into the RAM location......

 

Myk

 

I do not understand your claim, this threat is about "Sabnzbd+ plug-in to install Betas", right? so i add some modification into a existing one and publish it. If everyone puts his own plugin for Sabnzdb in a separate threat that would be a totally mess.

I know that this threat is about sabnzdb but i only mentioned about CouchPotato as an example tool which DATA DIR uses a lot of RAM and this is my explanation of previous post why I used the default path to cache disk nor RAM.

 

Of course it is possible to everyone to change the default path from /mnt/cache/.apps to his own.

you made a modification that caused config loss to some.  If you want to make that kind of change, start your own thead and advertise what yu have done.  I was about 30 secs into loosing my config when i came back to this thread.  It is normally good policy when you modify someone elses code to check with them first unless the project has been abandoned.

 

Myk

WARNING: If your data dir is set to /mnt/cache/.Apps/ then WW's version will overwrite your settings on reboot.

 

..Now to set it back up

 

Its not a huge deal, I didn't lose anything that can't be fixed, but why did you hard code the install directories to the cache drive instead of /usr/local/ like it was?

 

EDIT: I merged the changes you made into my plugin, not sure if I'm the only one with a capital "A" in the directory path, but just in case, this will stop that from happening to someone else.

 

You can get it here

 

Did you check it? That's weird beacuse i have always the same install dir as data dir and it never override my settings even if i install the newest versions of Sabnzdb in my data dir = install dir.

Its welcome for modifications to be made to the plugins! I hadn't had time to see why the update/beta install wasn't working anymore, and WW took the time and fixed it. I modified the plug-in from Benni-Chan, only reason I made a new thread was to support the fact that it did something completely different by installing the beta's, and it would be easier to keep track of bugs this way.

 

Changing the default directory was unfortunate for me, but wasn't a huge deal. I was exhausted when it happened which is why I was ill tempered about it.

 

I know most people use only lower case in linux, so it most likely won't be a problem for most.

 

I'm glad WW did fix the beta install. Granted, it would have been nice to know that WW changed the default install directory and data directory, but nothing to get riled up about,

 

I get the reason to put the data directory on a drive instead of ram. I still think that it shouldn't default to writing to a disk, just in case it could mess something up. If written to ram if something were to happen a reboot would fix it.

 

Either way, no need for hostility, you did come across the thread and no harm was done, my config is back how I like it, and we can install beta's again.

Did you check it? That's weird beacuse i have always the same install dir as data dir and it never override my settings even if i install the newest versions of Sabnzdb in my data dir = install dir.

 

It wasn't the fact that the install and data directory are the same, it was you made the default data directory /mnt/cache/.apps/ and mine has been /mnt/cache/.Apps/. Something there overwrote my config

I'd just like to mention (again) that not everyone has a cache drive, so any plugin should probably not default to that setup.

 

I hope all the different mods can be all pulled into one grand update, fixing all these little issues once and for all

 

Also, I think keeping all discussion in this thread, which is about the SABnzbdb BETA install, is the right course of action.

 

Thanks again for everyones' input!

Still doesnt apear to be working correctly for me

root@Tower:/etc/rc.d# rc.sabnzbd update
yes
installing latest Beta Version (0.6.15)
--2012-05-15 12:18:39--  http://downloads.sourceforge.net/project/sabnzbdplus/sabnzbdplus-beta/0.6.15/SABnzbd-0.6.15-src.tar.gz
Resolving downloads.sourceforge.net (downloads.sourceforge.net)... 216.34.181.59
Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|216.34.181.59|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-05-15 12:18:39 ERROR 404: Not Found.

tar: /tmp/SABnzbd-0.6.15-src.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
cp: cannot stat `/usr/local/SABnzbd-0.6.15/*': No such file or directory
rm: cannot remove `/usr/local/SABnzbd-0.6.15': No such file or directory
rm: cannot remove `/tmp/SABnzbd-0.6.15-src.tar.gz': No such file or directory

 

when I run the lines that get the versions manually, here is what I get:

root@Tower:/etc/rc.d# wget -q -O - http://sabnzbdplus.sourceforge.net/version/latest | awk '/0/{gsub(/\015/,"");print}'
0.6.15
http://sourceforge.net/projects/sabnzbdplus/files/sabnzbdplus/sabnzbd-0.6.15
0.7.0Beta5
http://sourceforge.net/projects/sabnzbdplus/files/sabnzbdplus-beta/0.7.0Beta5
root@Tower:/etc/rc.d# wget -q -O - http://sabnzbdplus.sourceforge.net/version/latest | awk '/1/{gsub(/\015/,"");print}'
0.6.15
http://sourceforge.net/projects/sabnzbdplus/files/sabnzbdplus/sabnzbd-0.6.15
root@Tower:/etc/rc.d#

Yeah I just ran into that, its fixed, uploading the new one now

Get it HERE

Yep that worked, thanks.

So does this have python 2.6.6?  How hard would it be to get python 2.7?

Influencer, about cache drive and RAM memory usage, here is another modified version of Sabnzdb install script. I added storage memory usage information for install and for data dir.

If data dir = install dir then there is only one summary value.

 

Of course install dir and data dir are set to /usr/local/

sabnzbd-0.7.2-ww.zip

I think that is a good addition, it lets users know how much space their installation is using.

I installed the sickbeard and sabnzbd plugins from another thread but after a reboot it deletes the configs and then wants to start setup all over again. Is there a way to avoid this upon reboot?

 

What does your config look like? Data directory MUST reside on a disk to survive reboot.

what about if their install/data dir does not start with /mnt/user/ (if the same) or their data dir if different and then warn them they will loose their config on reboot.

 

guess would also have to take into account if they have a extra drive mounted via SNAP, dont know how those are prefixed as I dont use it....

 

Just a thought....

 

Myk

 

That was the issue. I had to install or at least make the data directory on my user share.

I was thinking about that, using HDparm to see if the directory is on a drive or not, if not, a message appear at the top of the config. I'll play with it and see if its doable. I don't want to start sending those tcl warning messages,

 

EDIT: HDparm can't do what I want, I'll check out other options

Not sure if this will be enough to determine:

 

stat -f -c '%T' directory_or_file_to_examine

 

# stat -f -c '%T' /mnt/disk1/Anime/Music/Cowboy\ Bebop\ OST\ 1/01\ Tank\ \!.mp3

reiserfs

# stat -f -c '%T' /mnt/user/Anime/Music/Cowboy\ Bebop\ OST\ 1/01\ Tank\ \!.mp3

fuseblk

# stat -f -c '%T' /dev/shm/

tmpfs

# stat -f -c '%T' /proc/cpuinfo

proc

# stat -f -c '%T' /sys/kernel/notes

sysfs

 

You can try blacklisting some filesystem types such as: tmpfs, ramfs, proc, or sysfs. That way you wont have to get into white-listing other filesystem checks like for vfat, ntfs, ext2, ext3, ext4 or whatever may come down the road.

 

Thanks! That should do it, if its a ram filesystem, it won't survive a reboot. Anything else should. Flash drives should show as msdos(atleast mine does, and I assume others are formatted the same) so I can have a separate warning about log sizes and flash life expectancy decreasing

 

Now, would users prefer a nag-box(javascript alert box) to pop up on submission letting them know the selected data-dir will not survive a reboot, or just a message at the top of the config page?

 

I think I'd prefer the message at the top, but it would only appear after it was set. The javascript alert box could pop up before the form is submitted, with "ok" to continue and accept, or "cancel" to go back and change.