SRP_DAEMON_PORT@.SERVICE(5)

✨ SRP_DAEMON_PORT@.SERVICE(5) ✨

okay so this is the manual page for srp_daemon_port@.service, bestie — the little systemd template that keeps tabs on exactly one RDMA port at a time 💅

🌸 NAME 🌸

srp_daemon_port@.service — the srp_daemon_port@ systemd service that runs the show for a single port 🎀

🦋 SYNOPSIS 🦋

srp_daemon_port@.service

💖 DESCRIPTION 💖

So like. srp_daemon_port@.service is the one deciding whether an srp_daemon process is out here monitoring the RDMA port you dropped in as the template argument. That's its whole job, and it ate. 👑

The RDMA port name format is dev:port, where dev is the name of an RDMA device and port is a port number starting from one. Yes, starting from one. Not zero. Do not come for me. 🙈

Here's the vibe: starting an instance of this template starts an srp_daemon process. Stopping an instance of this template stops the srp_daemon process for the port you specified. That's it, that's the whole relationship, it's giving very committed. 🫶

And listen — if you wanna make sure srp_daemon never starts for a certain port, you can block it by masking the matching systemd service, like:

systemctl mask srp_daemon_port@mlx4_0:1

no cap, masking is the move when you need it gone-gone. 🚫

Wanna see every RDMA device and port number pair you've got? You can pull the list like this:

$ (cd /sys/class/infiniband >&/dev/null && for p in */ports/*; do
   [ -e "$p" ] && echo "${p/\/ports\//:}"; done)
mlx4_0:1
mlx4_0:2
mlx4_1:1
mlx4_1:2

look at those four little icons slaying in a list ✨ mlx4_0:1, mlx4_0:2, mlx4_1:1, mlx4_1:2. iconic.

🎀 SEE ALSO 🎀

• srp_daemon(1)
• srp_daemon.service(5)
• systemctl(1)

and that's the whole page, fr fr. this one came from srp_daemon and it's living in section SRP_DAEMON_PORT@.SERVICE(5) — go read it, it's short and it understood the assignment 💜