> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/px-5.2.1-en/startup/linux_inicio.md).

# Linux startup

## Startup parameters

The application **Editran/PX** is installed with a default configuration that sets the operating parameters by default.\
However, this configuration can be customized through the following variables in the script `<home-px>/EDItranPX`:

* **Log message level**. From lowest to highest, the possible levels are: INFO (1), TRACE (2), and DEBUG (3). By default, the system starts with INFO level (equivalent to defining `EDI_DBGL=1`).

  ```bash
  #################
  #EDI_DBGL: Uncomment to set log level INFO(1), TRACE(2), DEBUG(3)
  #EDI_DBGL=3
  #export EDI_DBGL
  ```
* Ability to periodically check, at intervals defined in minutes, whether there are **changes in the configuration** and apply them **without needing to restart the system**. By default, the system starts without this check (equivalent to defining `TCHECK_CFG=0`).

  ```bash
  #################
  #TCHECK_CFG: Uncomment to apply changes in the configuration. Interval in min
  #TCHECK_CFG=15
  #export TCHECK_CFG
  ```
* Ability to **enable/disable access to the name server**. By default, the system starts with this check enabled (equivalent to defining `CHECK_DNS=1`).

  ```bash
  #################
  #CHECK_DNS: Uncomment to enable/disable DNS lookup
  #CHECK_DNS=0
  #export CHECK_DNS
  ```

The values of these variables are applied at startup **Editran/PX**. Therefore, any modification requires a restart for the changes to take effect.

If any of these variables is not defined, **Editran/PX** its default value will be used.

## Startup and shutdown

The script `EDItranPX` allows you to define which processes should be started and stopped during startup and shutdown operations. For this, the variables **PROC\_STAR** and **PROC\_STOP**:

```bash
PROC_STAR="ediproxyth logsrv"
PROC_STOP="ediproxyth logsrv"
```

These are:

* **ediproxyth**: Process **Editran/PX**.
* **logsrv**: Allows status and configuration queries, and access to the log of **Editran/PX** from Editran z/OS and iSeries.

### Startup and shutdown in process mode

* To start Editran/PX, run: `EDItranPX start`
* To stop Editran/PX, run: `EDItranPX stop`
* To check the status of Editran/PX: `EDItranPX status`

### Startup and shutdown in service mode

* To start Editran/PX, run: `systemctl start editranpx.service`
* To stop Editran/PX, run: `systemctl stop editranpx.service`
* To check the status of Editran/PX: `systemctl status editranpx.service`

> ℹ️ *Note:* To be able to start **Editran/PX** it is necessary to have defined the [configuration](/documentacion-editran/px-5.2.1-en/configuration/configuracion.md) and have a [license](/documentacion-editran/px-5.2.1-en/installation/licencia.md) valid.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/px-5.2.1-en/startup/linux_inicio.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.