FreeNAS Code

add a validation for plugins path (it cannot be the same or reside within the jail path

Do-Not-Merge: plugin stuff

Auto-Commit of i18n data from Pootle for GUI

Fix some cornercases with adding users.

Here are the issues that pw doesn't catch that we care about:
- pw(8) doesn't restrict users from specifying regular files.
- pw(8) 'silently' fails (it complains via warn(3), but
doesn't return an exit code) if it can't create a home
directory (but only if the root path doesn't exist.. cute).
Example: pw doesn't create home directories if their base
directories don't exist, e.g. /mnt/tank/home/user where
/mnt/tank/home doesn't exist.

- Add a future hook for specifying the home directory mode,
as noted in ticket # 1117.

This doesn't fix modifying users, nor does it fix cleaning up
after users when deleted. This needs to be addressed in their
respective notifier APIs in future commits.

Tested with the following scenarios:

Sanity checks:
1. Create 'bar' with '/nonexistent'.
2. Create 'foo' with '/mnt/tank/foo'.
3. Create 'foo2' with '/mnt/tank/homes/foo', where
'/mnt/tank/homes' didn't already exist; this worked as
expected.

Negative tests:

1. Don't delete used directory:
a. Create 'foo' with '/mnt/tank/foo'.
b. mv /usr/sbin/pw /usr/sbin/pw.old .
c. Try to create 'foo2' with '/mnt/tank/foo'; this
failed but didn't nuke /mnt/tank/foo because it was
still in use.
2. Don't create user with a homedir pointing to a regular
file:
a. Try to create 'foo' with '/mnt/md_size'; failed as
expected.

lets try this to restart httpd on plugins install/delete events

Do-Not-Merge: That's what i heard!

make it refresh when a plugin is installed

Do not restart http here, it belongs elsewhere.

Do-Not-Merge: Don't put in TrueNAS

Force extraction.

Do-Not-Merge: Keep out of TrueNAS

Use system() to mv instead of os.rename.

Do-Not-Merge: Keeping out of TrueNAS

More empty row checks.

Do-Not-Merge: Keep out of TrueNAS

Only grab plugins if they are configured.

Do-Not-Merge: Keeping out of TrueNAS