Greyhole bug #675
Posted: Tue Nov 09, 2010 2:04 am
Please make Greyhole an optional component. There is no architectural reason to have this as a requirement. I don't like it - it's immature, has bugs and has caused data loss for people.
Since I use Amahi in a SOHO environment this is unacceptable.
This is a deal breaker for me. I love amahi, but if I have reasonable concerns about my data integrity and the changes I make to optional services I must abandon the project.
I understand that core services are kept "in check" by the amahi central config, but greyhole is not a core service in my opinion and it shouldn't be - people should be able to make the choice (either during first setup or later on) to choose for the storage pooling if they need it and/or want the software do the thinking for them.
Since I use Amahi in a SOHO environment this is unacceptable.
This is a deal breaker for me. I love amahi, but if I have reasonable concerns about my data integrity and the changes I make to optional services I must abandon the project.
I understand that core services are kept "in check" by the amahi central config, but greyhole is not a core service in my opinion and it shouldn't be - people should be able to make the choice (either during first setup or later on) to choose for the storage pooling if they need it and/or want the software do the thinking for them.