[systemd-devel] [RFC PATCH 2/2] journal: add async-signal-safe mode for sd_journald_sendv

2014-01-25 Thread Zbigniew Jędrzejewski-Szmek
signal(7) provides a list of functions which may be called from a signal handler. Other functions, which only call those functions and don't access global memory and are reentrant are also safe. sd_j_sendv was mostly OK, but would call mkostemp and writev in a fallback path, which are unsafe. Bein

[systemd-devel] [RFC PATCH 1/2] Replace mkostemp+unlink with open(O_TMPFILE)

2014-01-25 Thread Zbigniew Jędrzejewski-Szmek
This will only work on Linux >= 3.11, and probably not on all filesystems. Fallback code is provided. --- Hi, because on bug https://bugzilla.gnome.org/show_bug.cgi?id=722889, I was looking into async signal safety of the journal logging functions. All that do any formatting are unsafe, but sd_jou

[systemd-devel] merging libsd-id128 and libsd-login with libsystemd

2014-01-25 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Jan 16, 2014 at 04:41:48PM +0100, Lennart Poettering wrote: > So I am pretty sure libsystemd-id128, libsystemd-login, > libsystemd-journal should just end up in a single libsystemd.so together > with the event loop, the bus, the asyncns stuff and more. All this > functinality requires each

Re: [systemd-devel] SocketUser and SocketGroup?

2014-01-25 Thread Dave Reisner
On Sat, Jan 25, 2014 at 12:58:55PM -0800, Josh Triplett wrote: > Some daemons provide an access-controlled service via UNIX domain > sockets that have a specified user or group, and a mode like 0660. For > instance, clamd does this. systemd .socket units don't support setting > the user or group;

[systemd-devel] SocketUser and SocketGroup?

2014-01-25 Thread Josh Triplett
Some daemons provide an access-controlled service via UNIX domain sockets that have a specified user or group, and a mode like 0660. For instance, clamd does this. systemd .socket units don't support setting the user or group; systemd always creates sockets as root:root. This prevents replacing

Re: [systemd-devel] How can this be done with systemd

2014-01-25 Thread Roelof Wobben
From: [email protected] To: [email protected] CC: [email protected] Subject: RE: [systemd-devel] How can this be done with systemd Date: Sat, 25 Jan 2014 15:12:27 + > Date: Sat, 25 Jan 2014 16:05:29 +0100 > From: [email protected] > To: [email protected] > CC: sy

Re: [systemd-devel] Allow stop jobs to be killed during shutdown

2014-01-25 Thread Reindl Harald
Am 25.01.2014 18:09, schrieb Marcos Mello: > Koen Kooi dominion.thruhere.net> writes: > [snip] >> >> To make matters worse, the cylon eye isn't displayed when you boot with > 'quiet' in your kernel command line. > > "quiet systemd.show_status=1" shows the gracious Cylon eye so that should be

Re: [systemd-devel] Allow stop jobs to be killed during shutdown

2014-01-25 Thread Marcos Mello
Koen Kooi dominion.thruhere.net> writes: [snip] > > To make matters worse, the cylon eye isn't displayed when you boot with 'quiet' in your kernel command line. > "quiet systemd.show_status=1" shows the gracious Cylon eye. ___ systemd-devel mailing

Re: [systemd-devel] [PATCH 2/2] syscallfilter: port to libseccomp

2014-01-25 Thread Ronny Chevalier
2014/1/24 Lennart Poettering : > On Thu, 23.01.14 01:34, Ronny Chevalier ([email protected]) wrote: > >> --- >> Hi, >> >> This patch ports the syscall filter to libseccomp. It can be disable with >> --disable-seccomp and is enabled by default if libseccomp is present. >> >> Maybe I should a

Re: [systemd-devel] Allow stop jobs to be killed during shutdown

2014-01-25 Thread Ivan Shapovalov
On Friday 24 January 2014 at 18:46:06, Lennart wrote: > On Fri, 24.01.14 21:10, Ivan Shapovalov ([email protected]) wrote: > > > > > However, something like that can never be the default, we need to > > > > > give > > > > > services the chance to shut down cleanly and in the right order > > > >

Re: [systemd-devel] Allow stop jobs to be killed during shutdown

2014-01-25 Thread Dominique Michel
Le Sat, 25 Jan 2014 14:06:55 +, Colin Guthrie a écrit : > 'Twas brillig, and Lennart Poettering at 24/01/14 17:53 did gyre and > gimble: > > On Fri, 24.01.14 18:45, Reindl Harald ([email protected]) > > wrote: > > > >> However, something like that can never be the default, we need >

Re: [systemd-devel] Allow stop jobs to be killed during shutdown

2014-01-25 Thread Koen Kooi
Op 25 jan. 2014, om 15:06 heeft Colin Guthrie het volgende geschreven: > 'Twas brillig, and Lennart Poettering at 24/01/14 17:53 did gyre and gimble: >> On Fri, 24.01.14 18:45, Reindl Harald ([email protected]) wrote: >> >>> However, something like that can never be the default, we ne

Re: [systemd-devel] How can this be done with systemd

2014-01-25 Thread Roelof Wobben
> Date: Sat, 25 Jan 2014 16:05:29 +0100 > From: [email protected] > To: [email protected] > CC: [email protected] > Subject: Re: [systemd-devel] How can this be done with systemd > > On Sat, Jan 25, 2014 at 09:29:18AM +, Roelof Wobben wrote: > > Hello, > > > > I try t

Re: [systemd-devel] How can this be done with systemd

2014-01-25 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Jan 25, 2014 at 09:29:18AM +, Roelof Wobben wrote: > Hello, > > I try to port systemd to a live distro. > The biggest problem is that they work with modules. > > So before the start up can be processed all the modules needs to > be packed out and copied to memory. systemd-modules

Re: [systemd-devel] Allow stop jobs to be killed during shutdown

2014-01-25 Thread Colin Guthrie
'Twas brillig, and Lennart Poettering at 24/01/14 17:43 did gyre and gimble: >> > For me personally, the NFS timeout is a proper pain the backside. A >> > little more cleverness there would be appreciated. e.g. can we not just >> > do lazy umounts by default for NFS (or just e.g. a 5s timeout max o

Re: [systemd-devel] Allow stop jobs to be killed during shutdown

2014-01-25 Thread Colin Guthrie
'Twas brillig, and Lennart Poettering at 24/01/14 17:53 did gyre and gimble: > On Fri, 24.01.14 18:45, Reindl Harald ([email protected]) wrote: > >> However, something like that can never be the default, we need to give >> services the chance to shut down cleanly and in the right orde

[systemd-devel] How can this be done with systemd

2014-01-25 Thread Roelof Wobben
Hello, I try to port systemd to a live distro. The biggest problem is that they work with modules. So before the start up can be processed all the modules needs to be packed out and copied to memory. The script for that is this : #!/bin/bash# Activate a module, while running LiveCD.# Inc