Yatti420
Wizard
- Joined
- Aug 12, 2012
- Messages
- 1,437
Hello everybody..
Been playing with freenas 9.1.0-RC build.. Running really good.. Using a USB 3.0 Flash drive.. Nothing special but does work and boot with no issues..
GUI#1
Noticed a few things not sure if really a bug or issue for future releases.. The report graphs for system directories (root/etc/mnt...) are broken after first reboot.. Probably not a big deal as they wont be there i'm assuming upon official release?
GUI#2
I removed all (and disabled autotune since I had low ram - Shouldn't be on) sysctls carried over from old config and Removing tunables in the GUI is very slow for me.. Taking 5x longer then removing a sysctls..
Jail Storage Mounts
The only weird thing I can't figure out (which I hope isn't a rtfm question) is why certain jail directories (pictures) aren't "auto mounting" upon startup.. I can mount the offending directory easily by clicking it then checking mount.. Is there limitations with pathnames (no spaces etc?) Only mount certain amount of directories? Minidlna (with media_dir=) and transmission work no probs so far.. If I am downloading something I change the owner/perms manually before moving the files into perm storage..
Going to look into this output and dig into logs in a bit.. My NAS sits on .125 and jail on .126.. Jail is standard with VIMAGE/NAT disabled..
Thanks!
Been playing with freenas 9.1.0-RC build.. Running really good.. Using a USB 3.0 Flash drive.. Nothing special but does work and boot with no issues..
GUI#1
Noticed a few things not sure if really a bug or issue for future releases.. The report graphs for system directories (root/etc/mnt...) are broken after first reboot.. Probably not a big deal as they wont be there i'm assuming upon official release?
GUI#2
I removed all (and disabled autotune since I had low ram - Shouldn't be on) sysctls carried over from old config and Removing tunables in the GUI is very slow for me.. Taking 5x longer then removing a sysctls..
Jail Storage Mounts
The only weird thing I can't figure out (which I hope isn't a rtfm question) is why certain jail directories (pictures) aren't "auto mounting" upon startup.. I can mount the offending directory easily by clicking it then checking mount.. Is there limitations with pathnames (no spaces etc?) Only mount certain amount of directories? Minidlna (with media_dir=) and transmission work no probs so far.. If I am downloading something I change the owner/perms manually before moving the files into perm storage..
Going to look into this output and dig into logs in a bit.. My NAS sits on .125 and jail on .126.. Jail is standard with VIMAGE/NAT disabled..
Code:
Jul 25 22:30:01 NAS last message repeated 2 times Jul 25 22:30:01 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc alc0 Jul 25 22:30:01 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc alc0 Jul 25 22:30:01 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc 192.168.0.126 Jul 25 22:30:01 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc 192.168.0.126 Jul 25 22:30:02 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc 192.168.0.127/32 Jul 25 22:30:02 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc 192.168.0.127/32 Jul 25 22:34:56 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v Jul 25 22:34:56 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc alc0 Jul 25 22:34:56 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc alc0 Jul 25 22:34:56 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc 192.168.0.126 Jul 25 22:34:56 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc 192.168.0.126 Jul 25 22:34:56 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc 192.168.0.127/32 Jul 25 22:34:56 NAS manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/sipcalc 192.168.0.127/32 Stop refresh
Thanks!