### Múltiples Procesos - Un Ejemplo { #multiple-processes-an-example }

En este ejemplo, hay un **Proceso Administrador** que inicia y controla dos **Worker Processes**.

Este Proceso Administrador probablemente sería el que escuche en el **puerto** en la IP. Y transmitirá toda la comunicación a los worker processes.

Isso diz ao Traefik para escutar na porta 9999 e usar outro arquivo `routes.toml`.

/// tip | Dica

Estamos usando a porta 9999 em vez da porta padrão HTTP 80 para que você não precise executá-lo com privilégios de administrador (`sudo`).

///

Agora crie esse outro arquivo `routes.toml`:

```TOML hl_lines="5  12  20"
[http]
  [http.middlewares]

    [http.middlewares.api-stripprefix.stripPrefix]

/// tip | Consejo

Estamos utilizando el puerto 9999 en lugar del puerto HTTP estándar 80 para que no tengas que ejecutarlo con privilegios de administrador (`sudo`).

///

Ahora crea ese otro archivo `routes.toml`:

```TOML hl_lines="5  12  20"
[http]
  [http.middlewares]

    [http.middlewares.api-stripprefix.stripPrefix]

labels.searchoptions_menu_lang=Idioma
labels.searchoptions_menu_labels=Rótulos
labels.error_title=Erro
labels.system_error_title=Erro do sistema
labels.contact_site_admin=Entre em contato com o administrador do site.
labels.request_error_title=O formato da solicitação está incorreto.
labels.bad_request=A solicitação para a URL está incorreta.
labels.page_not_found_title=Página não encontrada.
labels.check_url=Verifique a URL.

=== ":material-language-kotlin: Kotlin"
    ```kotlin
      private val client = OkHttpClient.Builder()
          .certificatePinner(
              CertificatePinner.Builder()

            byte[] ident = new byte[] { 0, 0, 0, 0, 0, 5 };
            // Well-known group
            SID wkn = new SID(buildSidT((byte) 1, ident, 32), jcifs.SID.SID_TYPE_WKN_GRP, "BUILTIN", "Administrators", false);
            assertEquals("Administrators", wkn.toDisplayString());

            // BUILTIN with unknown type -> falls back to numeric toString

 * pinning certificates, you take on additional operational complexity and limit your ability to
 * migrate between certificate authorities. Do not use certificate pinning without the blessing of
 * your server's TLS administrator!
 *
 * ### Note about self-signed certificates
 *
 * [CertificatePinner] can not be used to pin self-signed certificate if such certificate is not
 * accepted by [javax.net.ssl.TrustManager].
 *

status shows `COMPLETED` only after the replication operation succeeds on each of the targets specified in the replication configuration. If multiple targets are configured to use active-active replication and multi destination replication, the administrator should ensure that the replication features enabled (such as replica metadata sync, delete marker replication etc) are identical to avoid asymmetric state. This is because all replication activity is inherently a one-way operation from source to...

 * {@code S-1-5-21-1496946806-2192648263-3843101252-1029} but they may
 * also be resolved to yield the name of the associated Windows account
 * such as {@code Administrators} or {@code MYDOM\alice}.
 * <p>
 * Consider the following output of {@code examples/SidLookup.java}:
 *
 * <pre>
 *        toString: S-1-5-21-4133388617-793952518-2001621813-512
 * toDisplayString: WNET\Domain Admins

labels.searchoptions_num={0} results
labels.searchoptions_menu_lang=Language
labels.searchoptions_menu_labels=Labels
labels.error_title=Error
labels.system_error_title=System Error
labels.contact_site_admin=Please contact your site administrator.
labels.request_error_title=Invalid Request Format.
labels.bad_request=Your request to the URL is invalid.
labels.page_not_found_title=Page Not Found.
labels.check_url=Please check the URL.
labels.user_name=Username