-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
bashisms in shell scripts #2922
Comments
Thank you for your contributions. |
This issue still exists in 10.2: bash-term-in-posix-shell '${gfid:0:2}' [usr/lib/x86_64-linux-gnu/glusterfs/gfind_missing_files/gfid_to_path.sh:24] |
A related issue #3598 |
Thank you for your contributions. |
ping |
Thank you for your contributions. |
@the-me1988 Is it okay to move the shell as bash shell? Will it lead to any problems? |
I submitted a PR #4449 which includes the scripts in this as well. |
Thats ok, it just means that glusterfs then "depends" also on bash. |
Hello,
with 10.0 there are some new bashishms in some shell scripts:
bash-term-in-posix-shell [sbin/mount.glusterfs:366] '[ "$syntax_status" =='
bash-term-in-posix-shell [sbin/mount.glusterfs:90] '[ "$servers" =='
bash-term-in-posix-shell [usr/lib/x86_64-linux-gnu/glusterfs/gfind_missing_files/gfid_to_path.sh:24] '${gfid:0:2}'
bash-term-in-posix-shell [usr/lib/x86_64-linux-gnu/glusterfs/gfind_missing_files/gfind_missing_files.sh:32] '/dev/tcp'
Debians advices for it are:
N: This script is marked as running under /bin/sh, but it seems to use a feature found in bash but not in the SUSv3 or POSIX shell specification.
N: Some examples are:
N: - == in a test, it should use = instead - read without a variable in the argument - function to define a function - source instead of . - . command args, passing arguments to commands
N: via source is not supported - {foo,bar} instead of foo bar - [[ test ]] instead of [ test ] (requires a Korn shell) - type instead of which or command -v
The text was updated successfully, but these errors were encountered: