super(config, andx);
    }

    /**
     * Returns the native LAN Manager string reported by the server.
     *
     * @return the nativeLanMan
     */
    public final String getNativeLanMan() {
        return this.nativeLanMan;
    }

    /**
     * Returns the native operating system string reported by the server.
     *
     * @return the nativeOs
     */
    public final String getNativeOs() {

        if (extendedSecurity) {
            System.arraycopy(buffer, bufferIndex, blob, 0, blob.length);
            bufferIndex += blob.length;
        }
        nativeOs = readString(buffer, bufferIndex);
        bufferIndex += stringWireLength(nativeOs, bufferIndex);
        nativeLanMan = readString(buffer, bufferIndex, start + byteCount, 255, useUnicode);
        bufferIndex += stringWireLength(nativeLanMan, bufferIndex);

        Files.writeString(jcifsPropertiesPath, "jcifs.smb.client.nativeOs=FileOS");
        System.setProperty("jcifs.properties", jcifsPropertiesPath.toString());

        System.setProperty("jcifs.smb.client.nativeOs", "SystemOS");

        Properties customProps = new Properties();
        customProps.setProperty("jcifs.smb.client.nativeOs", "CustomOS");

        SingletonContext.init(customProps);

## Monitoring MinIO in Kubernetes

MinIO server exposes un-authenticated liveness endpoints so Kubernetes can natively identify unhealthy MinIO containers. MinIO also exposes Prometheus compatible data on a different endpoint to enable Prometheus users to natively monitor their MinIO deployments.

## Explore Further

This directory contains JLine native libraries extracted from JLine JAR.

You can add your own build for platforms not natively supported by JLine.
See here [1] on how to compile for your platform and here [2] how libraries
follow JLine's directory and filename conventions.

[1] https://github.com/jline/jline3/tree/master/native

cpovirk <******@****.***> 1685135561 -0700

Yuri Schimke <******@****.***> 1735306796 +0200

Yuri Schimke <******@****.***> 1734771389 +0200

goktug <******@****.***> 1585082487 -0700

Und um über WebSockets mit Ihrem Backend zu kommunizieren, würden Sie wahrscheinlich die Werkzeuge Ihres Frontends verwenden.

Oder Sie verfügen möglicherweise über eine native Mobile-Anwendung, die direkt in nativem Code mit Ihrem WebSocket-Backend kommuniziert.

Oder Sie haben andere Möglichkeiten, mit dem WebSocket-Endpunkt zu kommunizieren.

---