Skip to content
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

Autoload CLI config-files after (auto) upgrade — autostart is enabled #1070

Open
PuzzledUser opened this issue Jul 27, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@PuzzledUser
Copy link

After doing an auto-upgrade (triggered in a GUI dialog after seeing an error in Notification Centre) only one of my configs is reloaded automatically*.

It would be great if autostart was triggered afterwards to load all (both) configs.

Currently I need to run (obviously I didn't need to run the first command):

% maestral start -c Work    
Daemon is already running.
% maestral start -c maestral
Starting Maestral...        [OK]
% maestral autostart        
Autostart is enabled. Use -N to disable.
% maestral --version    
1.9.4

*In fact, looking at the PID numbers (low number from autostart after boot), I see that the Work deamon was never stopped by the upgrade process. I guess it was still using the older version. So no configs are autoloaded after an upgrade.

@PuzzledUser PuzzledUser added the enhancement New feature or request label Jul 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant