Skip to content

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.
  • Labs icon Lab
  • A Cloud Guru
Google Cloud Platform icon
Labs

Using a Oneshot Systemd Service

Managing services with `systemd` is a skill that modern Linux system administrators require to enable or disable processes to run as a service on the system. Being able to troubleshoot systemd services is invaluable for correct system operation. In this activity, you will learn about managing systemd services by troubleshooting why a oneshot systemd service is failing. Once this activity is complete, you should be comfortable managing `systemd` services with `systemctl`.

Google Cloud Platform icon
Labs

Path Info

Level
Clock icon Intermediate
Duration
Clock icon 15m
Published
Clock icon Jan 17, 2020

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.

Table of Contents

  1. Challenge

    Use systemctl to check the status of target.service. Update the systemd oneshot service unit file named target.service.

    Using systemctl check the status of the target.service.

    systemctl status target.service
    systemctl status -l target.service
    

    Using the editor of your choice, update the /etc/systemd/system/target.service file to match the following contents.

    [Unit] 
    Description=Log when default target reached
    After=cloud-final.service 
    
    [Service] 
    Type=oneshot        
    RemainAfterExit=yes   
    ExecStart=/bin/echo "--->  Reached default.target"
    ExecStart=/bin/ls -l /etc/systemd/system/default.target 
    
    [Install]  
    # WantedBy is similar to runlevel
    WantedBy=default.target 
    
  2. Challenge

    Reload the `systemd` daemon for updated unit file to be available. Check to see if service will start.

    Use the systemctl command to reload the systemd daemon, so the new unit file can be managed.

    systemctl daemon-reload
    

    Use the systemctl command to start and check status of the target.service.

    systemctl start target.service
    systemctl status target.service
    
  3. Challenge

    Enable the `target.service` and reboot system.

    Using the systemctl command enable the target.service and reboot the system to verify operation of service at boot time.

    systemctl enable target.service
    reboot
    
  4. Challenge

    Reconnect to system and check the status of the `target.service`.

    First, you will need to use your lab credentials to reconnect to the system and access the root account. Then, use the systemctl command to view the status of the target.service. It should show that the target.service started correctly.

    sudo -i
    systemctl status target.service
    

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Provided environment for hands-on practice

We will provide the credentials and environment necessary for you to practice right within your browser.

Guided walkthrough

Follow along with the author’s guided walkthrough and build something new in your provided environment!

Did you know?

On average, you retain 75% more of your learning if you get time for practice.

Start learning by doing today

View Plans