Replies: 3 comments 3 replies
-
Sorry, you might actually be the first one. Feel free to post/link your solution here when you got one. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @nomis5000, Is this a duplicate of #1756, or if not, how is it different? |
Beta Was this translation helpful? Give feedback.
3 replies
-
>> My problem is that vorta won't start.
@nomis5000 thank you for confirming as well as explaining how your case
is different.
> Have you looked into the source of that issue? This could be a bug
> that needs fixing.
@yfprojects I think the nature of this issue is that the OP is
requesting managed execution. For example, if "systemd --user" was
managing a hypothetical vorta backend daemon, then
https://github.com/rfjakob/systembus-notify could use dbus to notify the
user in case of error. I'm sorry that I'm not aware of a generic
desktop application execution manager, and it seems the OP isn't either,
hence:
but I will come up with a useful script one day.
A wrapper script to catch and handle potential errors and notify the
user. This is the very important systems integration and real-world
user experience scope. I confess that I have been having to monitor
backup policy health by monitoring the borg repo dir on the backup
server, and have no idea how normal desktop users would ever know that
their backups are silently failing (ie: not happening).
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey, I just noticed that vorta installed via the arch user repository has not been able to start at boot for almost a month and so backups are missing for that period as well. Is there any way to check the proper running of vorta from time to time and display a warning if necessary? I can imagine that someone has already written a reliable script for such a case.
Beta Was this translation helpful? Give feedback.
All reactions