[root@freenas] ~# updatedb
updatedb: Command not found.
[root@freenas] ~#
[root@freenas] /etc/periodic/weekly# ls -l
total 5
drwxr-xr-x 2 root wheel 512 Jul 4 08:59 ./
drwxr-xr-x 6 root wheel 512 Jul 4 07:08 ../
-rwxr-xr-x 1 root wheel 548 Jul 4 08:55 310.locate*
-rwxr-xr-x 1 root wheel 550 Jul 4 08:55 340.noid*
-rwxr-xr-x 1 root wheel 886 Jul 4 08:55 400.status-pkg*
-rwxr-xr-x 1 root wheel 532 Jul 4 08:55 999.local*
[root@freenas] /etc/periodic/weekly# 310.locate
310.locate: Command not found.
[root@freenas] /etc/periodic/weekly#
[root@freenas] /etc/periodic/weekly# locate updatedb
locate: database too small: /var/db/locate.database
[root@freenas] /etc/periodic/weekly#
Edit /etc/periodic.conf and set weekly_locate_enable="YES" (the last line in the file). This will schedule weekly update of the locate database. After you do the edit you can also trigger immediate update of the database by running /etc/periodic/weekly/310.locate
You can then use the locate command to search for files. Please note that the DB upgrade runs as user nobody, so files that are not accessible by user/group nobody will not be in the DB. Also remember that the database will be wiped on reboot as it is stored in /var/db (ramdisk).
Actually I did this yesterday and it looks like it's "fixed" stuff now. Locate command seems to be working (although manually typing "updatedb" doesn't work)
Edit /etc/periodic.conf and set weekly_locate_enable="YES" (the last line in the file). This will schedule weekly update of the locate database. After you do the edit you can also trigger immediate update of the database by running /etc/periodic/weekly/310.locate
Sorry to bump but surely I'm not the only person who would like to make changes to the fundamental parts of FreeNAS which aren't in a jail?
This is possible right?
I'm not understanding your reply, can someone helpful please respond?