spylex

Members
  • Posts

    391
  • Joined

  • Last visited

Posts posted by spylex

  1. You can keep using ESXi the way you do now.  Adding Xen features to unRaid, letting it run as dom0, provides some nice flexibility in the product.

     

    I suppose my question was more like, can i do what i'm doing now, with unRAID. I.e. keep my VMs on separate hardware RAID1 arrays and run unRAID base.

  2. The reason i want to run unRAID as a VM is so that i can have all the great features ESXi has, like the ability to deploy VMs easily, assign separate datastores to VMs, passthru hardware and more.

     

    Why would my server boot into unRAID first and then all my VMs sit on it? I understand the advantages listed here http://lime-technology.com/forum/index.php?topic=31716.0, but they still don't make sense.

     

    For example, I want my Windows VM to sit on my RAID1 2x256GB SSD array i have setup, on a separate controller to unRAID. I want my Linux VM to sit on my RAID1 2x120GB SSD array i also have setup, on another controller. On the hand, i just want unRAID to work and sit as my most stable, untouched VM of the lot. This works just fine in ESXi but it seems like with unRAID 6 i would take a major step back by having all my VMs sit on the cache drive, no visual way of managing VMs, no reporting, nothing... until someone, sometime, builds a plugin.

     

    Am i missing something here?

  3. Ah, good old glftpd.  That name takes me back to pre-DSL days and helping sysop for topsites.  FXP, eggdrop bots, tcl race scripts and irc site invites.  Those were the days.  I guess probably still are if you know where to look.  Fond memories.

     

    Good memories indeed! Remember, the scene is still around and still using glftpd, although some have moved on.

     

    The reason i wanted it is for some statistics on my users, compared to what ProFTPD gives. And the scripts ;)

  4. The idea is to no longer create hidden folders, but rather 'Cache-only' shares. Then you can link to them from your plg settings as /mnt/user/<services>.

     

    From the 5.0beta8 update log:

     

    http://lime-technology.com/forum/index.php?topic=13866.0

     

    a) New feature called "cache-only" shares along with a re-written mover script.  The idea with a cache-only share is that the entire share exists only on the cache drive and is never moved to the array.  When a new share is created, and you have a cache disk, you are able to select 'only' for the "Use cache disk" setting.  In this case the top-level share name directory will only be created on the cache disk.  To support this, the 'mover' script is a bit different: it will never move top-level directories on the cache disk which don't also exist on the array.  Note to plug-in developers: if you have created a custom 'mover' script, please examine what is happening with the mover script of 5.0-beta8, since your custom script could now interfere with proper operation of the 'cache-only' share feature.

  5. Thanks tom for the updates :)

     

    Side question, looking back through the forums it was mention that 5.x was suppose to add SSD/Trim support (cache drives).. any status on that? or was that implemented and I over looked it.

     

    For best support of btrfs I need to update the base slackware platform and linux kernel.  unRaid 5.x is based on slack 13.1 (which is pretty old now), and unRaid 6 is based on slack 14.1 (which has just been released).  Turns out it's a fairly extensive job to upgrade the slackware platform, so this is what I want to do:

     

    - Release 5.0.1, which is primarily a bug fix release.

    - Freeze 5.x feature set and linux kernel at 3.9.11 (which is end of road for that kernel anyway).

    - Release 6.0, which is 64-bit kernel and slackware 14.1 platform (all 64-bit).

     

    When 6.0 is ready, I want to try and gauge how many users out there either can't run the 64-bit kernel, or experience big issues due to 64-bit kernel for some reason.  If "not many" users are negatively affected then:

     

    - Add new features such as cache pool only to 6.x series.

     

    If "many" customers can not run 64-bit, then I will be forced to go back and update 5.0 platform to slack 14.1.  I'm hoping I won't need to do that.  ;)

     

    This is fair. However, as other companies do, you could keep both 5.x and 6.x running at the same time, in different price brackets and feature brackets.

    • If you want to run unRAID on old hardware that doesn't support 64bit, you should still be able to get a stable build of unRAID. 5.x is your choice until you upgrade your hardware.
    • If you want the latest features and you've got the hardware for it, 6.x onward is your best bet.

     

    As long as both are stable, and both support the now independent webGUI, i think you've got a win-win for both yourself and the community. Trying to appease everyone with a single build might not work!

  6. @spylex:

    I'm still trying out glftpd. If I get it to work with user specific directories I will create a plugin for it. But it will take time. :)

     

    Mate, this is amazing! Just proftpd is not really good at reporting anything at this point... I think we'll be happier with glftpd. Plus it is what the scene uses ;)

  7. @spylex:

    glftpd looks nice, but I think it will be hard getting it to run on unraid. I'll give it a try and report back. :)

     

    edit:

    Using the install script in the archive it is possible to install glftpd on unraid. To get the server to work, a ssl certificate hast to be created. For this to work the openssl.cfg has to be symlinked to openssl.cnf. Then use the script provided by glftpd to create the cert. Add glftpd: ALL to hosts.allow.

     

    As the created files should be identical to each unraid installation it should be possible to put them in a plugin. I don't have the time to do this however. glftpd is nice, but I found no way to limit users to specific directories. A requirement I just need.

     

    Thats great! I understand about directories, however, it does work:

     

    http://glftpd.dk/files/docs/glftpd.docs look at 'privpath' is this what you mean? And also you can set a home directory for each user (/mnt/user/) and then privpath some of the directories there.

     

    Also you can set home directories and more.

     

    I just want to be able to see who is logged in, what speed they are downloading at, etc. All these things that are really hard in proftpd are easy on glftpd especially with the windows app!

  8. Influencer which combination of sickbeard/transmission/sab from the branches will stop the libc-2.11.1 segfaults again?

     

    Libc is not altered by atleast couchpotato, sabnzbd, sickbeard, transmission, plex media server or nzbmegasearch. These are the plug-ins I'm currently running and no libc faults and the libc version isn't 2.11.1. Is something else modifying libc?

     

    This only happens when i install transmission from the Upgrade branch, bizarre!