The Barrier object is a simple inter-process barrier implementation. It
allows placing synchronization points and waiting for the other side to
reach it. Additionally, it has an abortion-mechanism as second-layer
synchronization to send abortion-events asynchronously to the other side.
The API is
The Barrier-API simplifies cross-fork() synchronization a lot. Replace the
hard-coded eventfd-util implementation and drop it.
Compared to the old API, Barriers also handle exit() of the remote side as
abortion. This way, segfaults will not cause the parent to deadlock.
EINTR handling is
Hi
While working on a PTY helper I needed a synchronized fork() where parent and
child can both perform their setup before either proceeds.
src/shared/eventfd-util.c already provides a coarse API for that, but lacks many
features like implicit exit() handling. Therefore, I went ahead and wrote
This Pty API wraps the ugliness that is POSIX PTY. It takes care of:
- edge-triggered HUP handling (avoid heavy CPU-usage on vhangup)
- HUP vs. input-queue draining (handle HUP _after_ draining the whole
input queue)
- SIGCHLD vs. HUP (HUP is no reliable way to catch PTY deaths, always
Turns out, making strings shell-proof is harder than expected:
# machinectl set-hostname foo|poweroff . /etc/machine-info
(This could be simplified by quoting *and* escaping all characters,
which is harmless in shell but unnecessary.)
---
src/shared/fileio.c | 4 ++--
src/shared/util.h |
On 26.06.2014 15:30, Lukáš Nykrýn wrote:
poma píše v Pá 20. 06. 2014 v 13:36 +0200:
On 20.06.2014 13:31, Tom Gundersen wrote:
On Thu, Jun 19, 2014 at 1:37 PM, Vladimir Elisseev vo...@vovan.nl wrote:
Simple question: is there a way to set bridge parameters (bridge forward delay,
bridge hello
On Sun, Jun 29, 2014 at 01:05:22PM +0200, Tomasz Torcz wrote:
he.netdev:
--
[NetDev]
Name=he
Kind=sit
[Tunnel]
Local=109.107.25.67
Remote=216.66.80.162
he.network:
---
[Match]
Name=enp5s0
[Network]
Tunnel=he
Address=2001:470:70:68d::2/64
$
On Sun, Jul 13, 2014 at 04:56:16PM +0200, Sjoerd Simons wrote:
For the non-root user sysusers uses nologin as the default shell, not
login. Correct the documentation to match the code.
---
man/sysusers.d.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Applied.
Zbyszek
On Sat, Jul 12, 2014 at 07:36:16PM +0300, Tanu Kaskinen wrote:
---
man/systemd.unit.xml | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
Applied.
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
On Sat, Jul 12, 2014 at 06:59:19PM +0300, Tanu Kaskinen wrote:
We already encourage upstreams to keep the default configuration
separate from user customizations for software that is installed in
the system location. Let's allow that separation also for software
that is installed in the home
Hi,
Yes, sending abortion events asynchronously is really nice :-)
Just small quick comments for nspawn here, but I'll comment on patch #1
On Sun, Jul 13, 2014 at 12:37:07PM +0200, David Herrmann wrote:
The Barrier-API simplifies cross-fork() synchronization a lot. Replace the
hard-coded
On Sun, Jul 13, 2014 at 01:35:33PM -0700, Colin Walters wrote:
From b1113ed91ebdcf7ac2546a2618fe83751edfbaa0 Mon Sep 17 00:00:00 2001
From: Colin Walters walt...@verbum.org
Date: Fri, 11 Jul 2014 15:03:29 -0400
Subject: [PATCH] sysusers: Ensure /etc/{passwd,group} are labeled correctly
On Sun, Jul 13, 2014 at 06:49:00PM +0300, Mantas Mikulėnas wrote:
Turns out, making strings shell-proof is harder than expected:
# machinectl set-hostname foo|poweroff . /etc/machine-info
(This could be simplified by quoting *and* escaping all characters,
which is harmless in shell
13 matches
Mail list logo
