I made a script that shows the name of and file path to all system daemons, and their affiliated config files and paths

the script itself will be the comments.

Let me explain.

I wanted to know where all the daemons were. As far as I could tell, digging through all the systemd files was the only way. Daemons refer to config files. I wanted to know which ones. In figuring this out, I realized that I could not find an efficient way to show all system daemons, locations, all config files they use, and where those files are. As far as I can tell, there is no meaningful or convenient organization of daemons. So I thought, "wouldn't it be cool if I could run a command that shows me all the daemons, where they live, what config files they use, and where those config files are?"

So, my thought process was this:

1. "systemctl list-units --type=service" shows all system daemons.

2. Each unit file shows the file path to the daemon that systemd is starting.

3. Doing "strings | grep conf" at the daemon file shows the config files that daemon uses

4. Doing "find / -name [filename]" will find the config file

So I vibe-coded (asked an AI to make, and then modified) a script that does this and outputs the result like in the attached picture.

Now, I'm a crap coder (which is why I asked an AI), and I bet this script isn't great, but it works, and I think it's pretty cool that I can now reference this whenever I need to mess with a daemon.

Tell me if you think this is neat, useful, or dumb, and why.