From: heroxbd@gmail.com
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] report 8.10: improving OpenRC
Date: Sat, 11 Aug 2012 09:31:37 +0900 [thread overview]
Message-ID: <86y5lml15i.fsf_-_@gentoo.org> (raw)
In-Reply-To: <5024CB9F.4060906@gentoo.org> (Luca Barbato's message of "Fri, 10 Aug 2012 10:51:43 +0200")
Luca Barbato <lu_zero@gentoo.org> writes:
>> DONE, just foregrounded dropbear, and others is straightforward.
>>
>> the repo is at http://git.heroxbd.z.tuna.tsinghua.edu.cn/openrc.git
>> branch runit. Got feedback from bonsaikitten and ccxCZ on #openrc.
>
> looks interesting, in the long run might be nice to figure out how hard
> would be have startstopdaemon learn runit tricks.
Hmm, I don't think start-stop-daemon will. Because runit forks services
foreground while start-stop-daemon start backgrounded ones.
some reference: http://mywiki.wooledge.org/ProcessManagement
> Later we should fix the hardwired paths probably.
What kind of hardwired paths? /var/run/runit/xxx ?
>> supervising can really be done under runit, in a smooth way.
>>
>> (I'll use this openrc + runit on my home NAS to monitor ssh, mysql, nginx
>> and squid.)
>
> That's good to heard =)
:)
>>> I hope that will make more people happy, we definitely want more audience
>>
>> started, slower than I thought. hopefully today first draft can come out.
>
> Great!
a debian ITP bug here
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684396 waiting for
rleigh to review my package.
Today's plan,
1. EPREFIX export from runscript.sh
2. test the EPREFIX and update http://wiki.gentoo.org/wiki/OpenRC/Prefix
run runit supervised services on my NAS
3. write a similar helper as lsb.pl for OpenRC to let it understand
systemd unit.
--
XU Benda
Research Center for Neutrino Science
Tohoku University
JAPAN
http://www.awa.tohoku.ac.jp/~benda
next prev parent reply other threads:[~2012-08-11 3:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 8:58 [gentoo-soc] report 7.16-7.23: improving OpenRC heroxbd
2012-08-07 4:53 ` [gentoo-soc] report 7.24-8.7: " heroxbd
2012-08-07 9:16 ` Luca Barbato
2012-08-08 23:24 ` [gentoo-soc] report 8.8: " heroxbd
2012-08-09 6:05 ` Luca Barbato
2012-08-10 2:56 ` [gentoo-soc] report 8.9: " heroxbd
2012-08-10 8:51 ` Luca Barbato
2012-08-11 0:31 ` heroxbd [this message]
2012-08-11 23:50 ` [gentoo-soc] report 8.11: " heroxbd
2012-08-13 8:33 ` Luca Barbato
2012-08-15 15:14 ` [gentoo-soc] (draft) final report for OpenRC soc project 2012 heroxbd
2012-08-15 21:47 ` Luca Barbato
2012-08-16 8:38 ` heroxbd
2012-08-16 11:41 ` Rich Freeman
2012-08-17 5:39 ` heroxbd
2012-08-17 7:29 ` Luca Barbato
2012-08-17 11:56 ` Rich Freeman
2012-08-20 3:04 ` heroxbd
2012-08-20 8:16 ` Luca Barbato
2012-08-20 10:25 ` Fabian Groffen
2012-08-20 16:32 ` Luca Barbato
2012-08-20 18:25 ` Fabian Groffen
2012-08-20 10:47 ` Rich Freeman
2012-08-20 16:34 ` Luca Barbato
2012-08-20 18:12 ` Rich Freeman
2012-08-20 18:28 ` Luca Barbato
2012-08-20 16:15 ` EBo
2012-08-21 14:07 ` heroxbd
2012-08-21 15:55 ` Luca Barbato
2012-08-22 2:04 ` heroxbd
2012-08-22 7:35 ` Luca Barbato
2012-08-27 10:46 ` Patrick Lauer
2012-08-27 12:37 ` Rich Freeman
2012-08-27 13:29 ` Luca Barbato
2012-08-27 14:10 ` Rich Freeman
2012-08-27 14:35 ` Luca Barbato
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=86y5lml15i.fsf_-_@gentoo.org \
--to=heroxbd@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