You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
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
@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?
It appears that during the build the following command is run:
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: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 usingsudo
if necessaryThe text was updated successfully, but these errors were encountered: