systemd service for auto-start in Raspberry Pi - Step-by-Step Execution

Concept Flow - systemd service for auto-start

Create service file

↓

Define service details

↓

Enable service

↓

Start service

↓

Service auto-starts on boot

This flow shows how to create, enable, and start a systemd service so it runs automatically when the Raspberry Pi boots.

Execution Sample

Raspberry Pi

[Unit]
Description=My Auto Start Service

[Service]
ExecStart=/usr/bin/python3 /home/pi/myscript.py

[Install]
WantedBy=multi-user.target

This is a simple systemd service file that runs a Python script automatically.

Execution Table

Step	Action	Command/Content	Result
1	Create service file	sudo nano /etc/systemd/system/myservice.service	File opened for editing
2	Write service content	Add [Unit], [Service], [Install] sections	Service file saved
3	Reload systemd	sudo systemctl daemon-reload	systemd reloads new service files
4	Enable service	sudo systemctl enable myservice.service	Service set to start on boot
5	Start service now	sudo systemctl start myservice.service	Service starts running
6	Check status	sudo systemctl status myservice.service	Shows service is active
7	Reboot system	sudo reboot	System restarts and service auto-starts
8	Verify auto-start	sudo systemctl status myservice.service	Service is active after reboot

💡 Process ends after verifying service auto-starts on boot

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 5	After Step 8
Service File	Not created	Created with content	Enabled for auto-start	Running	Running after reboot
systemd daemon	Old config	Reloaded with new service	New config active	New config active	New config active
Service Status	Inactive	Inactive	Inactive	Active	Active

Key Moments - 3 Insights

Why do we run 'systemctl daemon-reload' after creating the service file?

Because systemd needs to reload its configuration to recognize the new service file, as shown in step 3 of the execution table.

What does 'enable' do compared to 'start'?

'Enable' sets the service to run automatically on boot (step 4), while 'start' runs the service immediately (step 5). Both are needed for auto-start.

How do we confirm the service runs after reboot?

By checking the service status after reboot (step 8), which shows it is active, confirming auto-start works.

Visual Quiz - 3 Questions

Look at the execution table, what command reloads systemd to recognize the new service?

A sudo systemctl enable myservice.service

B sudo systemctl start myservice.service

C sudo systemctl daemon-reload

D sudo reboot

💡 Hint

Check step 3 in the execution table where systemd reload happens.

At which step is the service set to start automatically on boot?

A Step 4

B Step 5

C Step 2

D Step 7

💡 Hint

Look at the action 'Enable service' in the execution table.

If you skip 'sudo systemctl daemon-reload', what will happen when you try to enable the service?

A Service will enable and start normally

B systemd will not recognize the new service file

C Service will start but not enable on boot

D System will reboot automatically

💡 Hint

Refer to the importance of step 3 in the execution table and variable_tracker for systemd daemon state.

Concept Snapshot

systemd service file syntax:
[Unit] - description
[Service] - command to run
[Install] - target for auto-start
Commands:
daemon-reload (reload configs)
enable (auto-start on boot)
start (run now)
Check status to verify

Full Transcript

To make a program auto-start on Raspberry Pi using systemd, first create a service file in /etc/systemd/system with sections [Unit], [Service], and [Install]. The [Service] section includes the command to run your program. After saving, run 'sudo systemctl daemon-reload' to reload systemd configuration. Then enable the service with 'sudo systemctl enable servicename' to set it to start on boot. Start it immediately with 'sudo systemctl start servicename'. Check status with 'sudo systemctl status servicename'. After reboot, the service will auto-start and can be verified again with status command.