mjhjmtu

I'm trying to understand systemd more and figure out how to modify the startup process. What I'm trying to do is prompt the user for an input before loading the login screen.
I went ahead and ran "systemctl list-dependencies getty@tty1.service" and got the below (not full output):

getty@tty1.service
├─system-getty.slice
└─sysinit.target

From what I understand, everything in the tree is either a hard/soft dependency, so I created a basic service unit file as such:

[Unit]
Description=Something to do

[Service]
ExecStart=/root/script.sh

[Install]
RequiredBy=getty@tty1.service

I went and enabled the service and re-checked the dependencies for getty@tty1.service and saw:

getty@tty1.service
├─system-getty.slice
├─wantedservice.service
└─sysinit.target

So I'm assuming now getty@tty1.service will not start until wantedservice is active (wantedservice is just a bash script asking for user input and then echoing it back out) due to the "RequiredBy" initiative, but it simply isn't the case; the login screen will still come up and when I check the status of wantedservice after login it just says inactive.

Here is "script.sh" just in case:

#!/bin/bash
echo "What is your name?"
read _name
echo "Hello $_name!"

So here are some questions I have:

1) How does systemd decide if a service is "active" (in my case, does it consider my service "active" after the script completes?"

2) I sometimes see my script pop up for a second before the login screen basically overtakes it, so it's loading, but its just not sticking around waiting for input, any idea what might be happening there?

I'm don't think it's relevant but all this is being done from a Debian 9 VM if it matters. Thanks all!