![]() The idea is that is never restarted, and always runs the base install version. Stopping with Control-C is not so good because it only kills the update-runner parent, leaving its server child. ![]() Starting a from the Command Prompt causes the paired parent/child, and activates fine. The only way here for a Windows service Duplicati to activate the update is to restart the service, reboot, etc. I don’t know if it was intentional for Windows service to have a single as well, but see this, and another possibility might be for the child to return special exit to ITS parent, thereby starting the newer version of and (I hope) the new. Is it ok that I see 5 processes of Duplicati in Windows Task manager? Here, the is just restarted in its original version by the child because the exit code it uses to request an update-restart only works between a paired child and parent, e.g.:ĭuplicati.Server twice? (which is maybe not quite correct because it can also just pass the exit code upwards) Process Monitor is a good way to see the exit code attempt (which goes to a spot that doesn’t process those). ![]() ![]() There might be a typo (“Note” as “Not”) in the report from but I wonder if those Duplicati service processes are two plus a ? Which ones restart at activate? Viewing in Process Explorer is easier (plus one can see where executable is from), but Task Manager suffices. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |