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

Daemon does not use port parameter #59

Merged
merged 1 commit into from
Sep 18, 2022

Conversation

crisdut
Copy link
Member

@crisdut crisdut commented Sep 12, 2022

Description

The peerd daemon uses only the default port instead of the port number parameter.

Steps to Reproduce

  1. Launch lnpd without --threaded argument.
  2. Run lnp-cli listen with --port argument.

**Expected: ** The lnpd launch peerd with defined port argument.
**Current: ** the microservice::supervisor try spawn peerd with port 9999 and causes rust panic (Unable to bind to Lightning network peer socket: Os { code: 98, kind: AddrInUse, message: "Address already in use" })

This PR fixies this.

Copy link
Contributor

@dr-orlovsky dr-orlovsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dr-orlovsky dr-orlovsky merged commit e8acc66 into LNP-WG:master Sep 18, 2022
@crisdut crisdut deleted the fix/daemon-unset-port branch January 26, 2023 04:23
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

Successfully merging this pull request may close these issues.

2 participants