New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sabnzbd truncates its own config file #186
Comments
sab stores config in memory and writes on exit. so yes you prob shouldnt run out of hd space on the drive you run sab. nothing we can do about user error |
how about not attempting to write the config file if the backup operation fails? seems like a reasonable check to make the software more resilient to failures. |
Could be a bug. |
when does sab backup the config (in sb we do it on every upgrade, thus the previous back could be months old)? |
@shypike Fedora 19 |
I tried to reproduce, but SAB already first tries to make the backup and only if that succeeds it will save a new config. Don't think we can make it safer than that.. |
This happened when I ran out of disk space. Noticed the config file was on disk, but empty. No backup file around. Found this in the logs:
The text was updated successfully, but these errors were encountered: