if command -v systemctl >/dev/null; then
        echo "### NOT starting on installation, please execute the following statements to configure fess service to start automatically using systemd"
        echo " sudo systemctl daemon-reload"
        echo " sudo systemctl enable fess.service"
        echo "### You can start fess service by executing"
        echo " sudo systemctl start fess.service"

        exit 1
    ;;
esac

# Stops the service
if [ "$STOP_REQUIRED" = "true" ]; then
    echo -n "Stopping fess service..."
    if command -v systemctl >/dev/null; then
        systemctl --no-reload stop fess.service > /dev/null 2>&1 || true

    elif [ -x /etc/init.d/fess ]; then
        if command -v invoke-rc.d >/dev/null; then
            invoke-rc.d fess stop || true
        else

    FESS_ENV_FILE="${packaging.env.file}"
    if [ -f "$FESS_ENV_FILE" ]; then
        . "$FESS_ENV_FILE"
    fi
fi

if [ "$REMOVE_SERVICE" = "true" ]; then
    if command -v systemctl >/dev/null; then
        systemctl --no-reload disable fess.service > /dev/null 2>&1 || true
    fi

    if command -v chkconfig >/dev/null; then
        chkconfig --del fess 2> /dev/null || true
    fi

`MINIO_VOLUMES="http://minio{1...2}/data{1...4} http://minio{3...4}/data{1...4}"`, you can remove the first argument `http://minio{1...2}/data{1...4}` to update your `MINIO_VOLUMES` setting, then restart all the servers in the setup in parallel using `systemctl restart minio`.

- On Kubernetes setups, the statefulset specification needs to be modified by changing the command line input for the MinIO container. Once the relevant changes are done, proceed to execute `kubectl apply -f statefulset.yaml`....