From: Manjeet Singh <itsmanjeet1998@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Openrc performance improvement
Date: Wed, 18 Mar 2020 11:01:42 +0530 [thread overview]
Message-ID: <CAKJVCPYvW610qMd90pOqHOyx1ftvQqcJwfp_dLizkvzZLA+z4g@mail.gmail.com> (raw)
In-Reply-To: <robbat2-20200317T185552-208358180Z@orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
i might be wrong with my words, i aim to say that openrc use openrc-run to
handle the service file as script and for this openrc-run will setup
environment like PATH and extra functions for the service script to execute
that eat some time, and that time can be overcome by developing a native
tool that will itself parse the service file, and handle it
i have proper roadmap for what and how achieve that, under this time period
i aim to develop a openrc-run like tools named openrc-service (or whatever
the developers like) that will read the service as a configuration file
only, and instead of executing it as shell script with start-stop-daemon,
openrc-service (new tool) use a inbuilt function to start the service as
background daemon, or stop it or and perform other actions.
i already tried a similar learning project:
https://github.com/itsManjeet/service
to show my concept.
aim is now to develop simple tool with a tight integration with openrc to
boost its performance, Development of this tool can surely be done within
the gsoc time period but developing a parser that read the current openrc
service file might take time, for this i will be ready to contribute after
the time period too.
thanks for your time and consideration
[-- Attachment #2: Type: text/html, Size: 1531 bytes --]
next prev parent reply other threads:[~2020-03-18 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 23:05 [gentoo-soc] Openrc performance improvement Manjeet Singh
2020-03-17 20:12 ` Robin H. Johnson
2020-03-18 5:31 ` Manjeet Singh [this message]
2020-03-17 23:51 ` Benda Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKJVCPYvW610qMd90pOqHOyx1ftvQqcJwfp_dLizkvzZLA+z4g@mail.gmail.com \
--to=itsmanjeet1998@gmail.com \
--cc=gentoo-soc@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox