}

    @Test
    public void testConstructor() {
        // Test if the constructor sets the file name and command correctly
        assertEquals(TEST_FILE_NAME, smbComQueryInformation.path);
        assertEquals(ServerMessageBlock.SMB_COM_QUERY_INFORMATION, smbComQueryInformation.command);
    }

    @Test
    public void testWriteParameterWordsWireFormat() {

rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...

rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...

rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...

        . "$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

    if command -v update-rc.d >/dev/null; then
        update-rc.d fess remove >/dev/null || true
    fi
fi

rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...

            dataCount = Math.min(totalDataCount, available);
        } else {
            if (command != SMB_COM_NT_TRANSACT) {
                command = SMB_COM_TRANSACTION_SECONDARY;
            } else {
                command = SMB_COM_NT_TRANSACT_SECONDARY;
            }
            // totalParameterCount and totalDataCount are set ok from primary

/**
 * SMB1 Logoff AndX request message.
 *
 * This command is used to terminate a user session that was
 * previously established with a Session Setup AndX command.
 */
public class SmbComLogoffAndX extends AndXServerMessageBlock {

    /**
     * Creates a new SMB1 logoff request to end a user session.
     *
     * @param config the CIFS configuration
     * @param andx the next command in the AndX chain, or null
     */

            this.mid = mid;
        }

        @Override
        public int getCommand() {
            return command;
        }

        @Override
        public void setCommand(int command) {
            this.command = command;
        }

        @Override
        public void setUid(int uid) {
            // No-op for test
        }

        @Override

    elif command -v chkconfig >/dev/null; then
        echo "### NOT starting on installation, please execute the following statements to configure fess service to start automatically using chkconfig"
        echo " sudo chkconfig --add fess"
        echo "### You can start fess service by executing"
        echo " sudo service fess start"

    elif command -v update-rc.d >/dev/null; then