-
Notifications
You must be signed in to change notification settings - Fork 51
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
Fix permission denied when echo
ing to /dev/stdout
#415
Fix permission denied when echo
ing to /dev/stdout
#415
Conversation
Instance
|
echo
ing to /dev/stdout
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to work fine:
ocaisa@LAPTOP-O6HF2IKC:~$ cat bash.func
function show_msg {
# only echo msg if EESSI_SILENT is unset
msg=$1
if [[ ! -v EESSI_SILENT ]]; then
echo "$msg"
fi
}
ocaisa@LAPTOP-O6HF2IKC:~$ source bash.func
ocaisa@LAPTOP-O6HF2IKC:~$ show_msg test
test
ocaisa@LAPTOP-O6HF2IKC:~$ EESSI_SILENT=1 show_msg test
ocaisa@LAPTOP-O6HF2IKC:~$
@boegel I'm not sure how this would actually get deployed so I'm reluctant to hit merge |
We basically need to redo the procedure for ingesting the init scripts: that means merging this PR, creating a new tarball using https://github.com/EESSI/software-layer/blob/2023.06-software.eessi.io/create_directory_tarballs.sh, and uploading the tarball to the S3 bucket using https://github.com/EESSI/eessi-bot-software-layer/blob/develop/scripts/eessi-upload-to-staging. |
tarball |
….18-GCC/12.3.0 {2023.06}[GCC/12.3.0] BCFtools V1.18
In some cases,
echo
ing to/dev/stdout
triggers a permission denied. Particularly, this happens when sourcing the init script (init/bash
) or the script to set key EESSI environment variables (init/eessi_environment_variables
). See #413This PR works around the issue by implementing a fix suggested in https://unix.stackexchange.com/a/38580
fixes #413