| 1 |
i might be wrong with my words, i aim to say that openrc use openrc-run to |
| 2 |
handle the service file as script and for this openrc-run will setup |
| 3 |
environment like PATH and extra functions for the service script to execute |
| 4 |
that eat some time, and that time can be overcome by developing a native |
| 5 |
tool that will itself parse the service file, and handle it |
| 6 |
|
| 7 |
i have proper roadmap for what and how achieve that, under this time period |
| 8 |
i aim to develop a openrc-run like tools named openrc-service (or whatever |
| 9 |
the developers like) that will read the service as a configuration file |
| 10 |
only, and instead of executing it as shell script with start-stop-daemon, |
| 11 |
openrc-service (new tool) use a inbuilt function to start the service as |
| 12 |
background daemon, or stop it or and perform other actions. |
| 13 |
i already tried a similar learning project: |
| 14 |
https://github.com/itsManjeet/service |
| 15 |
to show my concept. |
| 16 |
|
| 17 |
aim is now to develop simple tool with a tight integration with openrc to |
| 18 |
boost its performance, Development of this tool can surely be done within |
| 19 |
the gsoc time period but developing a parser that read the current openrc |
| 20 |
service file might take time, for this i will be ready to contribute after |
| 21 |
the time period too. |
| 22 |
|
| 23 |
thanks for your time and consideration |
Archives