---
title: "Daemons"
description: "How to use Corridor-Daemons to start, stop, and check the status of Corridor Platform processes."
---

This section describes how to use Corridor-Daemons to manage the corridor processes for each
component of the platform, as an alternative to an OS-level tool like [Systemd](/technology/installation/components/process-management/systemd/). Daemons can be used to:

- start
- stop
- check status
of the processes.

## Installation

There is no system dependency in case of Corridor-Daemons, so no additional installation is required.

## Configuration

No additional configurations are required when running Corridor processes using Corridor-Daemons.
We can use the below set of commands to start/stop/check_status.
The logfile and pidfile for each process can be saved at custom locations by using the parameters:

- logfile: location of the log file
- pidfile: location of the pid file

The default logfile directory is: `INSTALL_DIR/instances/INSTANCE/logs`

The default pidfile directory is: `INSTALL_DIR/instances/INSTANCE/pids`

To start the processes, we can do:

```sh
INSTALL_DIR/venv-api/corridor-api daemon start
INSTALL_DIR/venv-api/corridor-worker daemon start
INSTALL_DIR/venv-app/corridor-app daemon start
INSTALL_DIR/venv-jupyter/corridor-jupyter daemon start
```

To stop the processes, we can do:

```sh
INSTALL_DIR/venv-api/corridor-api daemon stop
INSTALL_DIR/venv-api/corridor-worker daemon stop
INSTALL_DIR/venv-app/corridor-app daemon stop
INSTALL_DIR/venv-jupyter/corridor-jupyter daemon stop
```

To check the status of the processes, we can do:

```sh
INSTALL_DIR/venv-api/corridor-api daemon status
INSTALL_DIR/venv-api/corridor-worker daemon status
INSTALL_DIR/venv-app/corridor-app daemon status
INSTALL_DIR/venv-jupyter/corridor-jupyter daemon status
```