---
title: "Christopher Smith (@et-ducky) | Hashnode"
description: "Christopher Smith (@et-ducky) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@et-ducky"
---

@et-ducky

# Christopher Smith

@et-ducky · Joined October 2026

## Comments

[sudo reads the password from the terminal unless it’s run with -S, so the prompt doesn’t take IDs from the loop’s stdin. The manual says -S reads it “from the standard input instead of using the terminal device”. The loop does need a terminal, so run the whole loop as root with sudo sh -c '...' when there’s no tty, such as from cron. The sessions in the source thread had no leader process and no session scope, so KillUserProcesses=yes wouldn’t have cleared them, but it’s a valid setting where leftover processes are what keep sessions in closing.](https://hashnode.com/posts/finding-why-ssh-logins-fail-at-the-systemd-logind-session-limit/6aeb546b11022764adffeec8/comment/6aec7f6adc7bf24d7442a068#reply-6aecace6180e3e227233bdef)

Reply · Article · Nov 5 · [Finding Why SSH Logins Fail at the systemd-logind Session Limit](https://hashnode.com/posts/finding-why-ssh-logins-fail-at-the-systemd-logind-session-limit/6aeb546b11022764adffeec8)
