romeograham Posted December 15, 2014 Report Share Posted December 15, 2014 Hello, I have a 500GB SSD and a 1TB HDD setup in my workstation. There are a few folders (on the HDD) that I have syncing to a NAS for Backup. I am running out of space on my SSD, and I see that I have a sync.log file that is 244.2 GB!!. I can't find anything about this (quickly) in the forum. Can I delete this file? Does it perform the same function as the .archive folders (as a backup)? Can I move it to my HDD, where I have more room? Should I uninstall BTSync (which is installed on my SSD) and reinstall it on my HDD? Thanks for any help! Quote Link to comment Share on other sites More sharing options...
Helen Posted December 15, 2014 Report Share Posted December 15, 2014 romeograham, Yes, you can delete it. Just quit Sync (no need to uninstall), and delete the log. Start Sync.No it's not similar to Archive. Log records all the events Sync does and goes through while syncing and is mainly used for debugging. Quote Link to comment Share on other sites More sharing options...
romeograham Posted December 15, 2014 Author Report Share Posted December 15, 2014 OK, excellent. Thanks for the quick reply! Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted December 15, 2014 Report Share Posted December 15, 2014 @romeograham, also to help keep your log sizes under control, make sure you've not enabled debug logging, and consider reducing the value of the advanced setting "log_size", which controls how large logs are allowed to become before being rotated. Quote Link to comment Share on other sites More sharing options...
mike20021969 Posted December 15, 2014 Report Share Posted December 15, 2014 consider reducing the value of the advanced setting "log_size", which controls how large logs are allowed to become before being rotated. What is the value measured in? In Sync 1.3.109, the default value is set at 10. But 10 what...?As 244.2GB is a whopper of a log file, I hope the value isn't terrabytes Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted December 16, 2014 Report Share Posted December 16, 2014 It's measured in Megabytes - the default in 1.3.x was 10, the default in recent builds of 1.4 is 100. 244.2GB is indeed a stupidly large log file - which is why it's worth checking you've not had debug logging constantly enabled without realizing. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.