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

LINC-Switch build fails on NFS (or other) file system without setuid/setcap permission #355

Open
lantz opened this issue Mar 4, 2015 · 1 comment

Comments

@lantz
Copy link

lantz commented Mar 4, 2015

It appears that during the build the following command is run:

sudo setcap cap_net_admin=ep ./rel/linc/erts-5.10.4/bin/beam.smp

Most NFS mounts (along with other shared file system mounts) don't permit setuid/setcap to be set on executables (this is a recommended best practice for configuration), so this command, and the make, fails with a confusing error message:

==> rel (generate)
Failed to set capabilities on file `./rel/linc/erts-5.10.4/bin/beam.smp' (Invalid argument)
The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
make: *** [rel] Error 1

It would be better if the build would actually complete and if you could either a) install the switch in a place like /usr/local/bin or /usr/bin, which are more likely to permit setuid, or b) if setuid/setcap fails, that the switch could be invoked using sudo if necessary

@lantz lantz changed the title LINC-Switch build fails on NFS volume without setuid/setcap permission LINC-Switch build fails on NFS or other volume without setuid/setcap permission Mar 4, 2015
@lantz lantz changed the title LINC-Switch build fails on NFS or other volume without setuid/setcap permission LINC-Switch build fails on NFS (or other) volume without setuid/setcap permission Mar 4, 2015
@lantz lantz changed the title LINC-Switch build fails on NFS (or other) volume without setuid/setcap permission LINC-Switch build fails on NFS (or other) file system without setuid/setcap permission Mar 4, 2015
@mentels
Copy link
Contributor

mentels commented Mar 9, 2015

@lantz I updated generating the release. Now when setcap cannot be executed on a file the user will be instructed to run the switch with sudo. Does it work for you?

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

2 participants