Indexing of "Read only"

[SunBob]

Hi,

first I'd like to thank you for your great and constantly enhanced Sync app.

I'm running BTsync on 3 clients, a PC, a Mac and a RPi. The RPi works as an always on server and is set up as "read only".

According to this "read only"-option I have a comprehension question. I understand that a first Indexing must take place, but why is my RPi indexing my folders on the server if nothing could be changed because of the "read only"-option? The problem with this is, that my RPI runs almost at 100% CPU usage just for indexing "nothing"?! :S

Hope somebody could bring light into darkness.

[Harold Feit]

RPi indexing my folders on the server if nothing could be changed because of the "read only"-option?

Most likely to verify that the folder has not gone out of sync with those that are read-write.

[SunBob]

Thx for your reply.

Just to be on the safe side, what does indexing mean?

A) Checking if a file of the RPi has changed, so that the "database" (I guess every "parameter" is stored in sth. like a database) has to be updated and the file can be synched to the other clients

or

B ) Checking if the database of client A is on par with client B

or

C) something else

I doubt it could be B, because the indexing is an ongoing process although every other client is "off".

And if it is A, I don't get why it is looking for "active" changes on the RPi since it doesn't matter as a result of the "read only" option.

(in condition that other changes of clients are directly saved to the RPi-database)

So if it is A or B I doubt that an ongoing indexing is necessary.

Please, tell me if I'm wrong or where my fallacy is.