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
Alternatively check for uname == SunOS and -d /usr/gnu/bin and then PATH=/usr/gnu/bin:$PATH
Operating system (please complete the following information): uname -a
SunOS serverle-g10p 5.11 omnios-r151038-c078b41acd i86pc i386 i86pc bash --version
GNU bash, version 5.1.4(1)-release (x86_64-pc-solaris2.11)
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
The text was updated successfully, but these errors were encountered:
elif [[ ${uname_res} == "SunOS" ]]; then
os="solaris"
if [ -d /usr/gnu/bin ]; then
export PATH=/usr/gnu/bin:$PATH
else
echo "required GNU Tools not found, exiting"
exit 1
fi
in my fork. If this acceptable, I can create a pull request.
Describe the bug
check_dns does not work for long resource record names. Validation of _acme-challenge.abrechnung.spi-kg.de. fails on SunOS.
To Reproduce
Steps to reproduce the behaviour:
code is
this does not work for
I think the
\W
is only correctly interpreted by GNU grep. The default grep on Solaris/OmniOS is POSIX.1 grep.using gawk the greps can be avoided and the command looks like this:
Alternatively check for
uname
== SunOS and -d /usr/gnu/bin and then PATH=/usr/gnu/bin:$PATHOperating system (please complete the following information):
uname -a
SunOS serverle-g10p 5.11 omnios-r151038-c078b41acd i86pc i386 i86pc
bash --version
GNU bash, version 5.1.4(1)-release (x86_64-pc-solaris2.11)
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
The text was updated successfully, but these errors were encountered: