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

rebar3 and remote_console #1970

Closed
silviucpp opened this issue Dec 6, 2018 · 3 comments
Closed

rebar3 and remote_console #1970

silviucpp opened this issue Dec 6, 2018 · 3 comments
Labels
dependency issue resides in a rebar3 dependency

Comments

@silviucpp
Copy link

Hello guys,

I have an erlang release where I enabled in vm.args the restricted shell using :
+Bi -stdlib restricted_shell module

This works nice but there is one problem:

when doing remote_console the same vm.args is applied including the above settings which makes impossible to exit from remote_console.

The old rebar only applies few settings from vm.args like cookie, name (mostly the one used to be able to connect) to the node. So there this was not the problem.

Do you have any suggestion ?

Silviu

@ferd
Copy link
Collaborator

ferd commented Dec 6, 2018

erlware/relx#649 (comment) I think this is the proper issue tracking it in the Relx library

@ferd ferd added the dependency issue resides in a rebar3 dependency label Dec 6, 2018
@tsloughter
Copy link
Collaborator

Correct. And I replied on the mailing list explaining the issue.

@silviucpp
Copy link
Author

Thanks guys !

@ferd ferd closed this as completed Apr 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency issue resides in a rebar3 dependency
Projects
None yet
Development

No branches or pull requests

3 participants