mirror of
https://github.com/evilhero/mylar
synced 2025-01-03 13:34:33 +00:00
Starting mylar with --backup would cause an exception
I tried to start Mylar with the --backup switch, but it caused an unhandled exception. So I updated the config_file to use the mylar.CONFIG_FILE, similar to the mylar.DB_FILE that is also backed up. Result: Starting Mylar with the --backup switch now copies the database and config files to the ./backup directory, as expected. Renaming existing files if necessary.
This commit is contained in:
parent
1ec6a1e087
commit
80f742110b
1 changed files with 1 additions and 1 deletions
2
Mylar.py
2
Mylar.py
|
@ -194,7 +194,7 @@ def main():
|
||||||
back = os.path.join(backupdir, 'mylar.db')
|
back = os.path.join(backupdir, 'mylar.db')
|
||||||
back_1 = os.path.join(backupdir, 'mylar.db.1')
|
back_1 = os.path.join(backupdir, 'mylar.db.1')
|
||||||
else:
|
else:
|
||||||
ogfile = config_file
|
ogfile = mylar.CONFIG_FILE
|
||||||
back = os.path.join(backupdir, 'config.ini')
|
back = os.path.join(backupdir, 'config.ini')
|
||||||
back_1 = os.path.join(backupdir, 'config.ini.1')
|
back_1 = os.path.join(backupdir, 'config.ini.1')
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue