Menu

#171 Request: Improvement of logging behaviour

1.2.6
Done
None
High
Review
2016-10-28
2016-10-21
No

I would suggest 4 1/2 thinks for the logging:

  1. At the moment the complete logging lines are writen into the log after the synch has finished completly! My last synch run took about 14 hours (over night) at today in the morning the log was still empty So there is no possibility to monitor what is done at the moment. Would it be possible to flush the line somethimes? E.g. after each file or every 5 minutes or something like that?

  2. The start is logged with

10/21/16 08:49:22 : Starting CryptSync

Would it be possible to add some more information? Source? Destination? Settings?

10/21/16 08:49:22 : Starting CryptSync. src:"c:\..." dst:"..." EncryptFilename:yes|no Encryption:7z|GnuPG Ext:cryptsync|7z fat:yes|no cpy:... skipFiles:... Mode:both ways|...|...
  1. there is no severity in a logline. Something like INFO, WARNING, ERROR would be good to be able to monitor the process

  2. The end of the sync isn't logged. It would be nice to see in the logfile that is has finished

4 1/2. At the end it would also be good to have a summary what was done! Eg:

10/21/16 08:49:22 : Finished CryptSync. State: no errors | xx errors Encrypted xxxx files with xxxx bytes

Or something like that.

Discussion

  • Stefan Kueng

    Stefan Kueng - 2016-10-28
    • status: New --> Started
    • assigned_to: Stefan Kueng
     
  • Stefan Kueng

    Stefan Kueng - 2016-10-28

    the log file is usually only saved when you click the "show log" button. If you don't do that, then the log is not saved but kept in memory.

    But I'll improve this now...

     
  • Stefan Kueng

    Stefan Kueng - 2016-10-28
    • status: Started --> Done
     
  • Stefan Kueng

    Stefan Kueng - 2016-10-28
     

    Related

    Commit: [r322]

  • Stefan Kueng

    Stefan Kueng - 2016-10-28
    • Milestone: 1.2.5 --> 1.2.6
     

Log in to post a comment.