ssh_systemctl_stop

Stop a specified systemd unit on a remote host via SSH with sudo access.

6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-systemctl-stop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssh_systemctl_stop
Source: https://github.com/Nightreaver/python-ssh-mcp/tree/main/skills/ssh-systemctl-stop
Command: npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-systemctl-stop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill allows you to stop a systemd unit on a remote host using SSH, providing a way to quickly take a service offline for maintenance or rollback configurations.

Core Features & Use Cases

  • Remote Systemd Unit Management: Execute systemctl stop commands on remote hosts.
  • Root Access Required: Ensures that the SSH account has sudo privileges or uses ssh_sudo_exec for interactive sudo.
  • Non-Disabling Stop: Stops the unit without disabling it for future boots.
  • Use Case: If you need to stop the nginx.service on a remote server for maintenance, you can use this Skill to do so without removing the service.

Quick Start

Stop the nginx.service on the remote host 'web01'.

Frequently Asked Questions about ssh_systemctl_stop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop a systemd unit on a remote host via SSH?

To stop a systemd unit on a remote host via SSH, you execute the systemctl stop command through the SSH connection. This halts the active service for maintenance or rollback purposes without disabling it for future system boots.

Do I need sudo privileges to stop a systemd service remotely?

Yes, you need sudo privileges to stop a systemd service remotely. Stopping a systemd unit is an administrative action requiring root access, so the SSH account must have sudo rights to execute the halt command successfully.

Will stopping a systemd unit through SSH disable it for future boots?

No, stopping a systemd unit through SSH does not disable it for future boots. The action only halts the currently running service for maintenance or configuration rollbacks, leaving the unit enabled to start automatically on the next system boot.

What is the best way to perform a maintenance shutdown of nginx on a remote server?

The best way to perform a maintenance shutdown of nginx on a remote server is to stop the systemd unit via SSH. This quickly takes the service offline for maintenance without removing it, requiring SSH access and sudo privileges on the target host.

When should I use SSH to stop a remote systemd unit instead of disabling it?

Use SSH to stop a remote systemd unit when you need a quick service deactivation for maintenance or configuration rollback. Stopping only halts the current process, whereas disabling prevents the service from starting on future system boots.