This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 181
Redir 3 forwarded ports are not being cleared correctly #467
Labels
Comments
ethervoid
changed the title
Redis ports are not being cleared correctly
Redir ports are not being cleared correctly
Jun 19, 2018
ethervoid
changed the title
Redir ports are not being cleared correctly
Redir 3 ports are not being cleared correctly
Jun 19, 2018
ethervoid
changed the title
Redir 3 ports are not being cleared correctly
Redir 3 forwarded ports are not being cleared correctly
Jun 19, 2018
More info: If you go to
but if you make a
Looks like the problem is the child process detaching after daemonizing itself |
ghost
self-assigned this
Jun 24, 2018
ghost
pushed a commit
that referenced
this issue
Jul 4, 2018
Thanks for the detailed report. It turns out that "foreground mode" was the key. I've noticed that it was a new option compared to v2.x, so that was a hint... and it was it. I've pushed a fix on |
Tested, seems to be working fine :) thank you |
Hey, sorry for the silence here but this project is looking for maintainers 😅 As per #499, I've added the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
We've been experiencing problems with redir, version 3.1, not being cleared after a
vagrant reload
I checked the code and found that is being done here.
The problem is that is getting the wrong PIDs from here
For example, my redir PID for port 3000 is
10459
but in the file redir_3000 is stored the PID10456
I'm going to paste some outputs here:
and the file cat
It seems like this part is not returning a correct PID for that process
Looks like spawn could be returning the parent pid instead of the final one?
The text was updated successfully, but these errors were encountered: