__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
# validate-workflow.sh
#
# validate workflow for Relax-and-Recover
#
# create a validation record to submit back to the project
#
# This file is part of Relax-and-Recover, licensed under the GNU General
# Public License. Refer to the included COPYING for full text of license.
WORKFLOW_validate_DESCRIPTION="submit validation information"
WORKFLOWS+=( validate )
WORKFLOW_validate () {
if test "$SIMULATE" ; then
LogPrint "${BASH_SOURCE[0]} submits validation information"
return 0
fi
Print "
Thank you for your time and effort to try out $PRODUCT and your
willingness to report about $PRODUCT in your environment back
to us. This kind of user support is greatly appreciated and helps a lot
to improve $PRODUCT.
--- The $PRODUCT development team
"
# Use the original STDIN STDOUT and STDERR when rear was launched by the user
# to get input from the user and to show output to the user (cf. _input-output-functions.sh):
read -e -p "Press ENTER to continue ... " 0<&6 1>&7 2>&8
Print "
The purpose of submitting validation info is to assist you with informing us
about the correct functioning of $PRODUCT (or major parts of it) to
establish a database of validated systems and environments.
Since nobody can test everything it is sufficient if you submit information
about $PRODUCT in exactly your environment and we will combine such
reports from all users into the information published on the website and within
the validation information that you can see at the end of '$PROGRAM dump'.
Please answer the following questions and email the resulting information to
the $PRODUCT development team at <contact@relax-and-recover.org>. You
should only include information that you are willing to see published on the
$PRODUCT website and contained within $PRODUCT.
"
# Use the original STDIN STDOUT and STDERR when rear was launched by the user
# to get input from the user and to show output to the user (cf. _input-output-functions.sh):
read -e -p "Press ENTER to continue ... " 0<&6 1>&7 2>&8
Print "
1. Submitter
-------------------
Please tell us (if you are willing), who you are and how to reach you. If you
want to remain anonymous you can put here nothing at all or only your initials
or no email or omit your company/organisation etc. However, the more 'personal'
a testimony to $PRODUCT in your environment, the more credible it
will be...
Example: Your Name <email-address>, Company/Organisation, Country
"
# Use the original STDIN STDOUT and STDERR when rear was launched by the user
# to get input from the user and to show output to the user (cf. _input-output-functions.sh):
read -e -p "Submitted By: " 0<&6 1>&7 2>&8
SUBMITTED_BY="$REPLY"
Print "
2. Features
-------------------
Please tell us (as exactly as possible) about the $PRODUCT features you
actually tested in your environment. Features are output and backup methods as well
as configuration types like LVM, MD etc.
Example: LVM, MD, SCSI, $BACKUP, $OUTPUT, EMAIL, ...
"
# Use the original STDIN STDOUT and STDERR when rear was launched by the user
# to get input from the user and to show output to the user (cf. _input-output-functions.sh):
read -e -p "Features: " 0<&6 1>&7 2>&8
FEATURES="$REPLY"
Print "
3. Comments
-------------------
Please let us know any comments you have about $PRODUCT in your
environment that would help others to better use $PRODUCT or have
less trouble installing it or maybe simply that you employ $PRODUCT
in a very large data centre with thousands of servers and that
$PRODUCT is the central component of your disaster recovery
preparations for your data centre.
Example: Need to install binutils, wodim and syslinux manually
Example: Works out-of-the-box flawless with all features
Example: We modified path/to/file in order to support foo-bar better
"
# Use the original STDIN STDOUT and STDERR when rear was launched by the user
# to get input from the user and to show output to the user (cf. _input-output-functions.sh):
read -e -p "Comments: " 0<&6 1>&7 2>&8
COMMENTS="$REPLY"
Print "
Thank you very much for your information. Please copy-and-paste the part
between the two lines into an email to contact@relax-and-recover.org.
Please feel free to add anything else you want to tell us about
$PRODUCT.
----------------------------------8<------------------------------------------
Version: $PRODUCT $VERSION / $RELEASE_DATE
Validation: $OS_VENDOR_VERSION_ARCH
Submitted: $SUBMITTED_BY
Date: $(date +"%Y-%m-%d")
Features: $FEATURES
Comment: $COMMENTS
---------------------------------->8------------------------------------------
You can also find this information in /tmp/rear-validate.txt
"
cat <<EOF >/tmp/rear-validate.txt
Version: $PRODUCT $VERSION / $RELEASE_DATE
Validation: $OS_VENDOR_VERSION_ARCH
Submitted: $SUBMITTED_BY
Date: $(date +"%Y-%m-%d")
Features: $FEATURES
Comment: $COMMENTS"
EOF
}