On fedora kinoite, If I type:
$ sudo mv name* /etc/systemd/system/
to move a .timer and .service file into that directory, systemctl will not be able to see them.
$ sudo systemctl enable --now name.timer
and
$ sudo systemctl status name.timer
will print in red "Unit name.timer could not be found."
The same happens for the .service files.
cat, nano, and kate could all see the files just fine after moving them with mv, it was only systemctl that could not.
If I use cp instead of mv, then systemctl was able to see the services files just fine. Same if I create the files manually with nano, they will be seen just fine.
After that I tested mv'ing the files and then opening the files with nano and ctrl+o rewriting them with no changes. This did not make systemctl see them.
I had to rm the files, and copying them in with cp or getting them back in there without using mv resulting in systemctl being able to see them just fine.
Also on Debian 13 kde, moving the files with mv results in systemctl being able to see them just fine with no issues, I have only tested Debian 13 and Fedora Kinoite 42.
I have worked around the issue successfully and do not need help solving it. I simply want to know why this happens for educational purposes, anyone know why this happens? Is this a bug?
$ sudo mv name* /etc/systemd/system/
to move a .timer and .service file into that directory, systemctl will not be able to see them.
$ sudo systemctl enable --now name.timer
and
$ sudo systemctl status name.timer
will print in red "Unit name.timer could not be found."
The same happens for the .service files.
cat, nano, and kate could all see the files just fine after moving them with mv, it was only systemctl that could not.
If I use cp instead of mv, then systemctl was able to see the services files just fine. Same if I create the files manually with nano, they will be seen just fine.
After that I tested mv'ing the files and then opening the files with nano and ctrl+o rewriting them with no changes. This did not make systemctl see them.
I had to rm the files, and copying them in with cp or getting them back in there without using mv resulting in systemctl being able to see them just fine.
Also on Debian 13 kde, moving the files with mv results in systemctl being able to see them just fine with no issues, I have only tested Debian 13 and Fedora Kinoite 42.
I have worked around the issue successfully and do not need help solving it. I simply want to know why this happens for educational purposes, anyone know why this happens? Is this a bug?
