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

Issue for mtr-packet while building customized version of mtr #470

Open
Arunmor1510 opened this issue Apr 23, 2023 · 0 comments
Open

Issue for mtr-packet while building customized version of mtr #470

Arunmor1510 opened this issue Apr 23, 2023 · 0 comments

Comments

@Arunmor1510
Copy link

When people try to build and test their own version of mtr, if they try to execute ./mtr directly from the building dir, they may ignore that the wrong mtr-packet binary is invoked if they have already installed another version of mtr don't have environment variable MTR_PACKET set, which potentially leads to wrong result.

It would be nice if there's a description on such behavior in README file, or make mtr try to load mtr-packet from current directory first.

This happened when I encountered an issue about SO_BINDTODEVICE, and I hope that mtr can get a new release version so Linux distros can update their mtr package.

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

No branches or pull requests

1 participant