wait until the transmission-daemon terminates properly #167
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Description:
We should wait for the termination of the transmission-daemon before the s6 service issues a sigterm to all remaining processes.
Without this delay the s6 sigterms are issued right after the RPC 'transmission-remote --exit'. This leaves not time to properly save the settings.json file, stats.json file, all resume files and showing the closing message 'Closing transmission session... done'.
Benefits of this PR and context:
This PR closes #80.
How Has This Been Tested?
docker-compose.yml:
Build:
Start:
Log after issuing
docker-compose downwithout the fix:Log after issuing
docker-compose downwith the fix:Important line in the logs when the saving occurs:
... Saved "/config/settings.json" ...Without the fix the old settings get reloaded right after the TERM signal by the S6 service.
This prevents saving changed settings from the Web-Interface:
... Reloading settings from "/config" ...Source / References:
#80 (comment)