Zero Length Files Seem To Be Handled Differently?

[rtrpm-bittorrentsync]

I use some flag files are just empty .txt files which have no content, zero length (e.g. touch my_lock.txt).  But I see that these are treated differently to files which aren't empty in 2 ways (V1.3.06):

 

1.  They don't feature in the history (tab) even though they get synced between devices.

 

2.  They don't get put into the .synarchive when they are deleted.

 

I'd like them to be the same as all other files which contain something.  I can force them to become like the others by adding some content, but that's another step I'd rather not have to do.

 

Is this a bug or by design, or a prob just on my systems (all Win7)?   Anyone else see this happening?

 

RTRPM.

[RomanZ]

@rtrpm-bittorrentsync

 

It is not a bug. Indeed, zero-length files are treated slightly differently. Simple rule - BTSync ignores them. Does not count against files amount, does not sync, move, mention in history, etc. It is done intentionally.

[rtrpm-bittorrentsync]

Thanks for the reply.

 

But it does actually sync them, I have just confirmed this in case I was mistaken but I'm not!  So if it does that then it really ought to mention the fact in the history.

 

rtrpm.

[RomanZ]

@rtrpm-bittorrentsync

 

I was not precise, sorry. Indeed - they are synced, but not mention anywhere for the user. The idea behind such behavior is that zero-length are used for service purposes (marking down directory, locks, etc.) and bear not much sense for the end user.