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

config: MistProcLivepeer in /usr/local/bin/ #53

Merged
merged 1 commit into from
Sep 29, 2022
Merged

Conversation

yondonfu
Copy link
Member

See livepeer/catalyst@83d3bcd

MistProcLivepeer needs to be invoked in /usr/local/bin after the above commit that changes where MistController is invoked from.

@yondonfu yondonfu merged commit 2e7f91d into main Sep 29, 2022
@yondonfu yondonfu deleted the yf/mist-proc-lp branch September 29, 2022 23:14
@@ -12,7 +12,7 @@ var Version string
var Clock TimestampGenerator = RealTimestampGenerator{}

// Path to Mist's "Livepeer" process that we shell out to for the transcoding
const PathMistProcLivepeer = "/usr/bin/MistProcLivepeer"
const PathMistProcLivepeer = "/usr/local/bin/MistProcLivepeer"
Copy link
Member

Choose a reason for hiding this comment

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

is it necessary to hardcode the full path to binary? wouldn't go be able to exec them from $PATH value?

Copy link
Member Author

Choose a reason for hiding this comment

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

If we can simplify this so that Go can exec MistProcLivepeer from $PATH instead of hardcoding a path here (which resulted in issues previously when the path that MistProcLivepeer was at changed), then that seems like a worthwhile improvement. @hjpotter92 mind tracking this is in an issue so this can be addressed?

Copy link
Member Author

Choose a reason for hiding this comment

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

Actually looks like this is tracked here livepeer/catalyst#172

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.

3 participants