Pugnacious

It's a recent change. The old version of the docker container had a capital letter instead of a lower case one. Thanks for pointing it out.

Thanks bud!

I too am getting this error. I did some checking from inside the docker container and indeed the awk command isn't present. perhaps the new version is missing that in the build? Did some more checking. logged into the docker by using the command: docker exec -it binhex-sabnzbdvpn bash then used the command: pacman -S awk accepted the file setup and restarted the docker. a more permanent fix would be to edit the startup script build/root/install.sh line 22: pacman_packages="git python2 python2-pyopenssl python2-feedparser p7zip ipcalc awk"

Try ZNC instead of Quassel.

I'm planning on combining my unraid with my desktop machine. The current hardware in my desktop machine is 8 core cpu 32gb ddr3 AMD RX470 gpu 1x 240gb ssd 1x 500gb sata Am I going to need to get a second graphics card for the unraid install to use, or will I be able to login to the web gui from my laptop and create my windows vm from there? It's currently running on a little i3 cpu and 8gb of ram. It already has a static IP, so it should pick that up once I transfer everything. What i'm unsure about is weather or not unraid will snag exclusive access of the GPU.

It's not very well documented, I had to search for hours just to find the relevant information. I'm going to take a couple leaps here and guess that you're more than a little experienced with Linux and ssh. Let me know if you don't understand something and i'll make it plainer. First, make sure that you have beets docker module installed and running. The installation should have been done with two folder variables. The first is the location it should import from and the second is the location it will store the imported music. Second, ssh into your unraid install. Third, type the following into your console(without quotes): "docker exec -i -t Beets bash" Fourth, in the new terminal prompt type(without quotes) "beet import /foldername" where /foldername is the import folder you setup for beets to import from. Once that starts, it will go black for a moment and then start to scan your music. It will then ask questions about the album and artist. Once you give it any needed information, it will take it from there.

Alright, thanks for the info. I'll give it a try right now. I was in the middle of thinking about doing it manually...shudder.

What is the fastest way to transfer files from a USB3.0 drive, formatted as NTFS to an unRAID machine, with no cache drive (building the machine as i have money to buy parts), and limited to 10/100 networking? Suggestions?

We wait in eager anticipation. But don't rush. Rushed work is shoddy work. I much prefer happy devs.

My wife has decided that the dedicated machine is in the way. I want to combine unraid with my new gaming machine. I haven't put the parts for the gaming machine together yet, and won't for a few days, however if it's possible, I plan on combining the machine with unraid and using my gaming machine as a VM on top of unraid. Is it possible to physically move the existing disks to the new hardware, without losing the data? or would it be a better plan to migrate the data off using a portable hard drive a few hundred gigs at a time? I still have two TB of files that I haven't added to the NAS yet, but I have around 1.2TB of files already on the NAS, and I would hate to loose those files. Hence the use of a dedicated NAS for them. The gaming machine will be a direct upgrade of my current machine, and there will be enough SATA ports for all the unraid disks plus my SSD for a boot drive. I haven't played with VM's on unraid at all. I'm just guessing that I will be able to give it a dedicated drive, and pass the single GPU through to the VM. Also, Do the VM's auto-start with unraid in the event that a power loss occurs? or would I be required to boot up a second machine and trigger the VM?

What is the best way to setup ssh to block certain IP's and allow others through. For various reasons I need remote ssh access to my files while i'm at work, but today I got a nifty surprise in the logs. Someone was trying to brute force my ssh login. Is there an easy way to combat that? Perhaps a way to deny access from a particular IP when three invalid login attempts happen?