SUMo : Keep your software up to date

Ditto.

 

I used the debug setting check-box, but displaying the log doesn't get logged when I try ctrl-L or use the menu. If I use ctrl-G or the menu to check for an update, that action does show up in the log. So I really don't know why Sumo is not finding the log on this system. I can display the log on W8.1-x64 but not on W7-x86 and W10-x64

 

Weird... "open logs" works fine on my Win10-x64.
Any other software hooking ctrl+L shortcut on your system ?

 

Not that I know of. Starting it from the help tab doesn't work either.

Edit: This problem was caused by by a reg mod that I did. I forgot to update the drive letter in the path of my default editor after moving it. Sorry for the false alarm.

 

Kyle, can the connection attempts to your servers be turned off or reduced?. After updating and checking my app-list, I blocked SUMO from continuously calling home every minute and haven't noticed any side effects. I don't understand why these connections are still necessary at this point. I would think a connection is only needed when running a check or during startup.

Spoiler

[

Code:

Error   [17-09-07 20:15:33]   Alt Server Offline
Error   [17-09-07 20:15:33]   DBCheck : Server error (10013)
Error   [17-09-07 20:15:33]   Main Server Offline
Error   [17-09-07 20:15:33]   DBCheck : Server error (10013)
Info   [17-09-07 20:15:33]   Alt Server Status Query
Info   [17-09-07 20:15:33]   Main Server Status Query
Error   [17-09-07 20:14:33]   Alt Server Offline
Error   [17-09-07 20:14:33]   DBCheck : Server error (10013)
Error   [17-09-07 20:14:33]   Main Server Offline
Error   [17-09-07 20:14:33]   DBCheck : Server error (10013)
Info   [17-09-07 20:14:33]   Alt Server Status Query
Info   [17-09-07 20:14:33]   Main Server Status Query
Error   [17-09-07 20:13:33]   Alt Server Offline
Error   [17-09-07 20:13:33]   DBCheck : Server error (10013)
Error   [17-09-07 20:13:33]   Main Server Offline
Error   [17-09-07 20:13:33]   DBCheck : Server error (10013)
Info   [17-09-07 20:13:33]   Alt Server Status Query
Info   [17-09-07 20:13:33]   Main Server Status Query
Error   [17-09-07 20:12:33]   Alt Server Offline
Error   [17-09-07 20:12:33]   DBCheck : Server error (10013)
Error   [17-09-07 20:12:33]   Main Server Offline
Error   [17-09-07 20:12:33]   DBCheck : Server error (10013)
Info   [17-09-07 20:12:33]   Alt Server Status Query
Info   [17-09-07 20:12:33]   Main Server Status Query
Error   [17-09-07 20:11:33]   Alt Server Offline
Error   [17-09-07 20:11:33]   DBCheck : Server error (10013)
Error   [17-09-07 20:11:33]   Main Server Offline
Error   [17-09-07 20:11:33]   DBCheck : Server error (10013)
Info   [17-09-07 20:11:33]   Alt Server Status Query
Info   [17-09-07 20:11:33]   Main Server Status Query

 

Ah! Thanks. Good you sorted that out.

 

As soon as i have blocked the connection with a firewall, i can see "Offline":

After unblocking it:

Yeah, SUMo is continously checking for an active connection.
I think it can be reduced to a minimum, if the check is only done after the user has started SUMo. Additionally a check can be added after the user has clicked on "Scan".
So we have a maximum of 1-2 checks.
Edit: Now i see that it was already mentioned

 

This is done in order to automatically connect to the faster server when users tries to connect for a "check". Retrieves no more than a "ping" and should not create much burden... am i wrong ?

 

Does SUMo works fine anyway in this case ?

 

As far as I can tell, yes. You really only need to check for the fastest server when a user requests a function that actually requires a connection such as Check. Even though you say there is no burden querying the servers continuously, this IMO is an unnecessary use of system resources and not what I would call a good idea.

 

OK, i'll think deeper about this.

 

SUMo - 5.3.5 (Released 2017-09-10)
==================================

http://www.kcsoftwares.com

 

Thanks very much, Kyle.
Download, installation and running the program are all fine.

One minor issue at the SUMo download page:
I notice the version is 5.3.5.3678, however, the SUMo download page says 5.3.5.367, which is not correct.

And I notice that the default download page and download link have a plain http URL, while SSL https is available for download page and download link URL. Is there a reason the default is http, instead of SSL https?

 

Both items fixed ! Thanks !!

 

Great! Thanks.

 

Looks like WizTree issue is fixed with v3.10, just released.

 

Ah nice that the website now uses TLS
Does this mean it can also be implemented for SUMo?
https://www.kcsoftwares.com/bugs/view.php?id=3052

 

I'm working on a prototype, at least for comms with the main server. On good tracks

 

Good !

 

Hi Adric,
I understand you don't want any system resources used if not absolutely necessary. Kyle said he will look into this.
What I wonder, how much is this an issue if the user closes SUMo after a couple of minutes? I guess this is typical use. I suppose SUMo stops connecting to the servers as soon as the application is closed? Please correct me if I'm wrong. If SUMo should not stop connecting after the application is closed, that I would surely consider to be an issue.
I understand that you don't want any more connections to the SUMo servers than absolutely necessary, but I wonder how this is really an issue if typically the user closes SUMo after only a couple of minutes.
Nevertheless, if you think it is an issue, I'm glad Kyle will look into this.

 

Yes, as soon as SUMo is closed (application not running) all communications with server are gracefully closed.
While SUMo is running it periodically "ping" its servers.

 

Ah, OK. Thanks for clarifying, Kyle.

 

You're welcome !

 

Great, thanks!

 

I'll keep you informed on this.