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

About 7-10s after closing MR.2, the port is still unavailable #12

Open
3 tasks
Michaelmilk opened this issue May 25, 2019 · 1 comment
Open
3 tasks
Labels
question Further information is requested

Comments

@Michaelmilk
Copy link

Prerequisites

  • Did you search in issues?
  • Are you running the latest version?
  • I will write this according to this template.

Environment

  • Mr.2 Version: latest
  • Server Operating System: win10
  • Server Operating System Version:
  • Server Operation System Language:
  • Client Operating System:
  • Client Operating System Version:
  • Client Operation System Language:

Expected Behavior

Current Behavior

Detailed Description

Possible Solution

Hey, I close MR.2 using CTRL-C in win 10 cmd. if start it immediately, it prints the port is still in using. After about 7-10 seconds, I can start it normally. Is this expected? Is there command to close it immediately?
Note:there is no other process using the same port.

@Michaelmilk Michaelmilk added the question Further information is requested label May 25, 2019
@txthinking
Copy link
Owner

txthinking commented May 26, 2019

Yes, this is intentional. The heartbeat interval is 10s.
But this behavior may be changed to close immediately by catch CTRL-C signal in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants