Google Desktop
Doesn't look like a keeper. It's taken days to fully index and is taking a boat load of disk space to do so:
(and you have to su root to see this much info.. it's not exposed via the gui that I've seen.)
drw------- 13 root wheel 442B Apr 7 17:47 .
drwxr-xr-x 3 root wheel 102B Apr 4 07:27 ..
-rw-rw--w- 1 root wheel 329B Apr 7 12:35 Volinfo.plist
-rw-r----- 1 root wheel 40K Apr 7 16:59 indexr1_btesmam
-rw-r----- 1 root wheel 28B Apr 7 16:59 indexr1_btesmao
-rw-r----- 1 root wheel 477M Apr 7 17:22 indexr1_db
-rw-r----- 1 root wheel 160K Apr 7 17:23 indexr1_db-journal
-rw-r----- 1 root wheel 576M Apr 7 17:47 indexr1_fti
-rw-r----- 1 root wheel 10M Apr 7 17:47 indexr1_fti-journal
-rw-r----- 1 root wheel 32K Apr 7 12:35 indexr1_prop
-rw-r----- 1 root wheel 512B Apr 7 12:35 indexr1_prop-journal
-rw-r----- 1 root wheel 594M Apr 7 16:52 indexr1_repo
-rw-r----- 1 root wheel 32K Apr 7 17:23 indexr1_repo-journal
(and you have to su root to see this much info.. it's not exposed via the gui that I've seen.)
posted by Lee at 5:48 PM
3 Comments:
God Bless you early adopters.
sudo ls -lAh
Index size aside, I'm concerned that standard checks of locked-down file systems tend to produce errors for Google Desktop-related
indexr1_db
I have posted to a relevant group.
Post a Comment
Links to this post:
Create a Link
<< Home