prestart path should not be near unitfiles

[jsoref]

https://github.com/jordansissel/pleaserun/search?q=prestart.sh&unscoped_q=prestart.sh

Files in systemd directories should be things like:
.service, .slice, .target, .wants, .timer, .socket, etc. -- each of which is a file type defined, managed, and parsed by systemd.

A simple start would be to replace unit_path with prestart_path so that it's at least vaguely easy to separate.

[jordansissel]

Can you help me understand the negative impact of the described problem?

…

On Wed, Dec 26, 2018 at 5:48 PM Josh Soref ***@***.***> wrote: https://github.com/jordansissel/pleaserun/search?q=prestart.sh&unscoped_q=prestart.sh Files in systemd directories should be things like: .service, .slice, .target, .wants, .timer, .socket, etc. -- each of which is a file type defined, managed, and parsed by systemd. A simple start would be to replace unit_path with prestart_path so that it's at least vaguely easy to separate. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#138>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIC6luP5qLYx6md0ZPoRDXQ6N9Bb3P0ks5u9Cb_gaJpZM4ZiOUg> .

[jsoref]

The short of it is that /etc/systemd/system and similar is for configuration files, not executable files.

Beyond that, systemd at times adds additional file extensions, so essentially it reserves the directories for its own purpose, if you aren't placing a file type that it promises to support, you potentially interfere with a future behavior of systemd.