Eagle shouldn't check Internet connection until fully opened

[samykamkar]

I don't mind Eagle checking the Internet connection, but this should happen in the background after Eagle has started up. Because Eagle should run fine for 14 days since last connect, it only needs to perform the 14-day check on startup without making any network connections, and if it detects it checked in within the last 14 days, then it should startup immediately, shaving seconds of startup time off. Once Eagle is fully up and the user is accessing it, then it can perform the check in the background to update the local last-checked-in-date.

[jorge_garcia]

Hi Samy,

The devs are tracking this forum, and its a good idea. Thank you for posting your suggestions.

Best Regards,

[Anonymous]

Hi.

They are allready adressin this, see this thread if interested: [BUG] Eagle leaking UDP sockets

[samykamkar]

I wouldn't tie this to the other ticket. The other ticket is primarily about excessive UDP connections causing an issue and that the check should happen less. This ticket is explicitly about *when* the check should occur. (Also, in my quick testing I found the validity check is over TCP, not UDP, but perhaps it happens over UDP if it can't make the TCP connection? Not sure...)

[Anonymous]

Eagle is just asking the Linux kernel if an interface is up, nothing more, haven't seen any outbound connection attempts for the connection test, only the UDP ones asking the Kernel network stack.

I'm also touching on the subject regarding when Eagle should check for network connectivity, that is why I put a link to it here 🙂