It is not a windows command. it is dotnet. an SDK provided by Microsoft, for many platforms, including Linux, FreeBSD, Windows, etc.
The context within the scripts are not important. It does not matter what I put in there, they do not launch.
The reason I call a script to then open another script is because I specifically do not want to include globalization support. furthermore, i do not want that path exported or used as a function. Again, only telling you this as information, not asking for assistance in that regard. Though I do appreciate your concern.
Please ignore any consideration of binaries. As I stated, I am not a novice in the linux world.
Technitium DNS Server is a DNS Server branded by a developer. Each of his servers begin with his chosen name ‘Technitium’.
To verify, it is a DLL, but DOTNET handles it just fine and is intended for linux. This is not WINE, it is not emulation, it is not translated. It is native and supported natively with a core instalation of DOTNET 7.0 (as of this writing). But again, please ignore what my scripts launch or do.
This inquiry is specifically as to why my SystemV and/or init.d scripts are not loading. Everything seems correct.
Furthermore, yes, I know IPFIRE provides Unbound, and many other features. This is a niche request. I have disabled Unbound, and replacing it with this DNS server. Just informational, not asking for assistance in that regard.
I just need to be able to launch this (and potentially other) commands via init.d. that is the problem launching via init.d. As I have expressed, the script(s) and services launch just fine, but only manually. They should be running at boot, which is RUNLEVEL 3.