On 04.08.22 11:09, Tanuj Bagaria wrote:
What do we as a community need to do
to get S6 into a "corporate friendly" state?
What can I do to help?
Here are some ideas:
- easier access to the VCS (git, pijul, etc)
I would not (yet) consider pijul common and stable enough to count
toward that
On 24.02.22 06:16, Jan-willem De Bleser wrote:
Not an option to be its parent since there's no persistent supervisor of a
jail's root process, but that script using .s6-svscan/finish should do
nicely. Thanks for the suggestion!
I use s6-rc on the FreeBSD jail host as well to manage jails with th
The s6-svscan and s6-supervise are very simple (and elegant) and in a
way do less than runsvdir and runsv: they don't go around allocating
resources at runtime.
On 30.06.2017 22:38, Steve Litt wrote:
On Fri, 30 Jun 2017 19:50:17 +
"Laurent Bercot" wrote:
The runsv executable is pretty
On 11/10/16 09:33, Andy Mender wrote:
Hello,
I am a "journeyman" UNIX user, currently trying to implement runit
as a substitute for systemd on a number of GNU/Linux distributions.
I already have the ./run service scripts per the original documentation for
runit (http://smarden.org/runit/).
Howev
On 01/09/16 15:43, Roger Pate wrote:
On Thu, Sep 1, 2016 at 8:34 AM, Laurent Bercot
wrote:
OK, now let's have a look at LISTEN_FDS.
I also find these particular implementation details a poor choice. I
was going to recommend a different environment convention, but then I
saw the pre-existing
On 25/08/16 23:17, Adrian Chadd wrote:
On 25 August 2016 at 14:13, Warner Losh wrote:
On Thu, Aug 25, 2016 at 3:08 PM, Adrian Chadd wrote:
On 25 August 2016 at 12:48, Lars Engels wrote:
On Thu, Aug 25, 2016 at 08:46:10AM -0700, Adrian Chadd wrote:
On 24 August 2016 at 21:53, Jonathan de Bo
On 25/08/16 06:53, Jonathan de Boyne Pollard wrote:
http://adrianchadd.blogspot.co.uk/2016/08/freebsd-on-tiny-system-whats-missing.html?showComment=1471236502051#c1305086913155850955
, Adrian Chadd:
We're using s6 at work, and it works out mostly ok. Mostly once you
get around the linuxisms, an
On 22/08/16 16:29, Martin "eto" Misuth wrote:
On Mon, 22 Aug 2016 07:26:12 -0700
Colin Booth wrote:
My own $0.02 is that s6-svscan -S should ignore power state signals
(including SIGINT which it currently doesn't ignore).
I haven't really understood this thread, but I think I am starting to
On 22/06/16 03:51, Thomas Lau wrote:
I am try to reproduce situation when runsv under some catastrophic failure,
when runsv got killed, it will restart, but my test daemon "memcached"
still running on background, eventually it will start memcached twice. How
could I avoid this from happening? See
On 21/06/16 16:24, Martin "eto" Misuth wrote:
On Tue, 21 Jun 2016 14:45:59 +0200
Laurent Bercot wrote:
...
With udevd, the workaround is to kill it after you have performed the
coldplug, and only restart it as part of your normal boot sequence once
you have pivot_rooted. It can be supervise
On 14/03/16 17:42, Jan Olszak wrote:
Hi!
We're running s6 in an lxc container.
lxc-stop sends SIGPWR to the init process (s6-svscan) to stop the
container, but SIGPWR isn't handled. It just gets discarded as if nothing
happened.
Is there a reason it works this way?
Thanks!
Jan
Probably beca
On 25/02/16 15:47, Steve Litt wrote:
Hi all,
Could somebody, in one or two sentences, tell me the difference between
s6 vs s6-init?
For the subject i infer that you're asking for the difference between s6
and s6-rc because there is no project or binary named s6-init.
I'm not looking for
Is there a way to update /etc/s6-rc/compiled without risking a broken
system if the power fails midway through the update?
The best I can come up with is to use a symlink to a uniquely named
compiled directory and a recompile wrapper along those lines:
cd /etc/s6-rc
s6-rc-compile .compi
On 09/11/15 15:33, Casper Ti. Vector wrote:
Suppose there are several services, and I want their log (complete or
only those fulfilling certain conditions) to be combined, for example in
the following scenarios:
* Those services are low-volumed (eg. getty's).
* Some important part of these logs
On 08/09/15 14:50, Laurent Bercot wrote:
On 08/09/2015 14:10, Jan Bramkamp wrote:
How would the ./run script or more likely the daemon it exec()ed into
die from a failed child process?
The child process could s6-svc -t if it fails to find readiness, for
instance. There should be an option
On 08/09/15 14:05, Laurent Bercot wrote:
On 08/09/2015 13:51, Jan Bramkamp wrote:
If the script fails for any reason the service is stuck and won't
come up. Such simple scripts shouldn't fail but they might still run
into resource limits or other (temporary) problems.
If the poll
On 07/09/15 16:36, Martin "eto" Misuth wrote:
Hi,
new s6 user here.
I started using s6 to do FreeBSD jail services management. It seems this helped
me to get rid of some socket timeout errors (?) in my jails setups.
In my deployment I am using "jail as vm" approach.
This works pretty well i
On 08/09/15 13:24, Laurent Bercot wrote:
On 08/09/2015 10:49, Jan Bramkamp wrote:
- Have one polling daemon.
- A wrapper registers polled services with the polling daemon.
No can do, sorry.
You can't make a supervision infrastructure depend on daemons,
because daemons depend
On 03/09/15 20:23, Laurent Bercot wrote:
On 03/09/2015 18:25, Buck Evan wrote:
An s6-checkhelper wrapper that implements exactly the above would make me
happy enough.
Yes, that's envisionable. I'll think about it.
I pondered over the problem and came up with the following conclusions:
-
The runit documentation (http://smarden.org/runit/replaceinit.html)
recommends users to replace the FreeBSD /sbin/init with runit-init. This
works at first glance but breaks the FreeBSD upgrade procedure.
The correct way to use alternative init exectuables is to change the
init_path kernel environ
20 matches
Mail list logo
