> For the complete documentation index, see [llms.txt](https://wiki.smhuda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.smhuda.com/programming/automation/untitled.md).
# Running a Service at Boot
Your `.service` file should look like this:
```
[Unit]
Description=Spark service
[Service]
ExecStart=/path/to/spark/sbin/start-all.sh
[Install]
WantedBy=multi-user.target
```
Now, take a few more steps to enable and use the `.service` file:
1. Place it in `/etc/systemd/system` folder with say a name of `myfirst.service`
2. Make sure that your script executable with:
```
chmod u+x /path/to/spark/sbin/start-all.sh
```
3. Start it:
```
sudo systemctl start myfirst
```
4. Enable it to run at boot:
```
sudo systemctl enable myfirst
```
5. Stop it:
```
sudo systemctl stop myfirst
```
#### Notes
1. You don't need to launch Spark with `sudo` in your service, as the default service user is already root.
2. Look at the links below for more `systemd` options.
#### Moreover
Now what we have above is just rudimentary, here is a complete setup for spark:
```
[Unit]
Description=Apache Spark Master and Slave Servers
After=network.target
After=systemd-user-sessions.service
After=network-online.target
[Service]
User=spark
Type=forking
ExecStart=/opt/spark-1.6.1-bin-hadoop2.6/sbin/start-all.sh
ExecStop=/opt/spark-1.6.1-bin-hadoop2.6/sbin/stop-all.sh
TimeoutSec=30
Restart=on-failure
RestartSec=30
StartLimitInterval=350
StartLimitBurst=10
[Install]
WantedBy=multi-user.target
```
To setup the service:
```
sudo systemctl start spark.service
sudo systemctl stop spark.service
sudo systemctl enable spark.service
```
#### Further reading
Please read through the following links. Spark is a complex setup, so you should understand how it integrates with Ubuntu's init service.
*
*
*
---
# 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://wiki.smhuda.com/programming/automation/untitled.md?ask=&goal=
```
`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.