Sign in to follow this  
rtrpm-bittorrentsync

Zero Length Files Seem To Be Handled Differently?

Recommended Posts

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.

Share this post


Link to post
Share on other sites

@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.

Share this post


Link to post
Share on other sites

@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.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this