Here we go..

[JTBTek]

I have decided to torture myself more than I already do..lol. Totally new to Freenas or any NAS for that matter. I have always thought about going with a NAS, but never felt I had much need. Now I have realized it is not a need, it is a want. If for no other reason that to learn something new. BUT learning something new has been one heck of a learning curve. I'm not completely new to unix cli, but wow.

I was donated a Dell T3500 with a Xeon X5670@2.93GHz and 24GB ECC memory. So, like any tech junky... Boom.. Not only do I wanna have a NAS. I can have a home media server and all the little extras.

I already have several questions that I have yet to find answers for. So I will stop here and continue my searching and post.

 

[kdragon75]

http://doc.freenas.org/
This will be your best friend. If you don't check that link first, I get cranky.

 

[JTBTek]

The DOC's have already proven very useful. Thank you, Last thing I wanna do is make an expert cranky.

 

[JTBTek]

It is alive!!

Dell Precision T3500 upgraded with a X5670 2.93GHz 6 core / 12 threads, with 24GB of ECC memory and 2 x 3TB seagate ironwolf HDs and 120GB Sandisk SSD.

FreeNAS 11.2-RC2
Transmission + OpenVPN and IPFW kill switch
Sonarr
Radarr
Plex Media Server

Everything almost works 100%, The only issue I have is when transmission finishes the download and move it from incomplete to complete directory, it is missing the group write permission. So as a temporary fix for this, I created a cron job for every 15 minutes to chmod the media directory recursively 777. This allows sonarr and radarr the ability to import it and move the files to their permanent directory, where plex is mounted.

So great seeing it all work.

 

[kdragon75]

Look into the umask program. It will set the default file permissions for the folder.

 

[JTBTek]

Look into the umask program. It will set the default file permissions for the folder.

Thanks for the tip! I'll look into it.

 

[JTBTek]

Amazing what can been found with just a simple word to point someone in the right direction. I had never heard about umask before.

I found this post here on the forums. Which listed these command:

login to the jail as root:
sudo jexec deluge tcsh

then:
ee ~/.cshrc

then:
change the umask from 22 to 2

finally:
save and restart the jail.


But I wanted to know more about what I was changing before I just jumped into the terminal and started plugging way. A g00gle search reviled this page. It is a great read on how umask works, and really gave me a better understanding of the changes I was gonna make.

This is just the bit of the site that I found most useful:

The umask command affects default permissions.

The shell command umask 022 sets to 022 (----w--w-) the permissions to be removed (masked) from the default permissions, for new files and directories created by the shell (and by commands run from that shell). It prevents write permission being assigned to group and other on newly created directories and files. A new directory would have permissions 777 (rwxrwxrwx) masked by 022 (----w--w-) resulting in 755 (rwxr-xr-x) permissions. A new file would have permissions 666 (rw-rw-rw-) masked by 022 (----w--w-) resulting in 644 (rw-r--r--) permissions.

The umask only applies to the permissions given to newly created files and directories.

The traditional friendly Unix umask is 022, resulting in default file permissions of 644 and default directory permissions of 755. (Newly-created files and directories are readable by anyone; but, they are only writable by the owner.) A “secure” umask would be 077. (Mask out all group and other permissions; newly-created files and directories are readable/writable/executable only by the single user that created them.)

The umask command cannot affect the permission of already-existing files. To do that, you must use the chmod command:

$ chmod 711 program$ chmod go-rwx secrets

Note that the umask and the permissions assigned by chmod are opposites. The chmod command sets permissions to be given to an object; the umask sets permissions not to be given to new objects.