> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/mailscheduler/getting-started/setup/summary/running-on-linux.md).

# Running on Linux

### Run through Service Manager

MailScheduler supports the following service managers: systemd and SysVinit/InitD. However, the application includes wrappers around the service managers, allowing you to perform the same actions using the application command line.

These commands provide flexibility in managing MailScheduler, allowing you to interact with the service directly or leverage service managers for control:

{% tabs %}
{% tab title="Via Application" %}
**Start Service**

If the service is not running, you can start it using:

```bash
sudo ./mailscheduler-amd64 service start
```

**Stop Service**

To stop the MailScheduler service:

```bash
sudo ./mailscheduler-amd64 service stop
```

{% endtab %}

{% tab title="Systemd" %}
**Service status**

To check the status of the MailScheduler service:

```bash
sudo systemctl status mailscheduler
```

**Start Service**

If the service is not running, you can start it using:

```bash
sudo systemctl start mailscheduler
```

**Stop Service**

To stop the MailScheduler service:

```bash
sudo systemctl stop mailscheduler
```

**Restart Service**

To restart the MailScheduler service:

```bash
sudo systemctl restart mailscheduler
```

{% endtab %}

{% tab title="SysVinit" %}
**Service status**

To check the status of the MailScheduler service:

```bash
sudo service MailScheduler status
```

**Start Service**

If the service is not running, you can start it using:

```bash
sudo service MailScheduler start
```

**Stop Service**

To stop the MailScheduler service:

```bash
sudo service MailScheduler stop
```

**Restart Service**

To restart the MailScheduler service:

```bash
sudo service MailScheduler restart
```

{% endtab %}

{% tab title="InitD" %}
**Service status**

To check the status of the MailScheduler service:

```bash
sudo /etc/init.d/MailScheduler status
```

**Start Service**

If the service is not running, you can start it using:

```bash
sudo /etc/init.d/MailScheduler start
```

**Stop Service**

To stop the MailScheduler service:

```bash
sudo /etc/init.d/MailScheduler stop 
```

**Restart Service**

To restart the MailScheduler service:

```bash
sudo /etc/init.d/MailScheduler restart
```

{% endtab %}
{% endtabs %}

### Service Commands

Always ensure you are in the application folder before executing service commands:

```bash
cd /usr/local/share/mailscheduler
```

**Installing and Uninstalling the Service**

Check the current status of the service, whether it’s installed or not:

```bash
sudo ./mailscheduler-amd64 service status
```

Manually install the application onto the server:

```bash
sudo ./mailscheduler-amd64 service install
```

Manually uninstall the application from the server:

```bash
sudo ./mailscheduler-amd64 service uninstall
```


---

# 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.infotopics.com/mailscheduler/getting-started/setup/summary/running-on-linux.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.