---
src/core/execute.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/core/execute.c b/src/core/execute.c
index c02c768..474a4af 100644
--- a/src/core/execute.c
+++ b/src/core/execute.c
@@ -1569,7 +1569,7 @@ int exec_spawn(ExecCommand *command,
On Wed, Feb 05, 2014 at 11:44:33PM +0100, Richard Weinberger wrote:
Hi!
We're heavily using Linux containers in our production environment.
As modern Linux distributions move forward to systemd have to make sure that
systemd works within our containers.
Sadly we're facing issues with
On Thu, Feb 06, 2014 at 04:33:22PM +0100, Greg KH wrote:
On Thu, Feb 06, 2014 at 10:55:01AM +, Daniel P. Berrange wrote:
On Wed, Feb 05, 2014 at 11:44:33PM +0100, Richard Weinberger wrote:
Hi!
We're heavily using Linux containers in our production environment.
As modern Linux
On 02/05/2014 01:53 PM, David Herrmann wrote:
Hi
On Wed, Feb 5, 2014 at 11:11 AM, Hannes Reinecke h...@suse.de wrote:
The 'active' sysfs attribute should refer to the currently
active tty devices the console is running on, not the currently
active console.
The console structure doesn't
On Thu, Feb 06, 2014 at 03:58:59AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Feb 06, 2014 at 03:27:07AM +0100, Greg KH wrote:
On Thu, Feb 06, 2014 at 01:31:37AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
Patch applied.
On Mon, Feb 03, 2014 at 10:33:37AM +, Jóhann B.
On 02/06/2014 04:29 PM, Greg Kroah-Hartman wrote:
On Thu, Feb 06, 2014 at 03:27:43PM +0100, Hannes Reinecke wrote:
The 'active' sysfs attribute should refer to the currently
active tty devices the console is running on, not the currently
active console.
That's not what
On Thu, Feb 06, 2014 at 04:44:20PM +0100, Hannes Reinecke wrote:
On 02/06/2014 04:29 PM, Greg Kroah-Hartman wrote:
On Thu, Feb 06, 2014 at 03:27:43PM +0100, Hannes Reinecke wrote:
The 'active' sysfs attribute should refer to the currently
active tty devices the console is running on, not
On Thu, Feb 06, 2014 at 04:54:59PM +, Jóhann B. Guðmundsson wrote:
On 02/06/2014 03:39 PM, Greg KH wrote:
Right now you have to decide before loading the module how many
devices you want. And also when trying to use a device (any device),
you have to look for one. The same issues as with
Am 06.02.2014 18:45, schrieb Greg KH:
On Thu, Feb 06, 2014 at 04:54:59PM +, Jóhann B. Guðmundsson wrote:
On 02/06/2014 03:39 PM, Greg KH wrote:
Right now you have to decide before loading the module how many
devices you want. And also when trying to use a device (any device),
you have
In the parse_env_file_push() and load_env_file_push() functions, there
are two assert() call to check if the key or value parameters are utf8 valid.
If the strings aren't utf8 valid, assert does abort.
These function are used early by systemd to parse some files. For
example '/etc/locale.conf'.
---
man/crypttab.xml | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/man/crypttab.xml b/man/crypttab.xml
index 5f386e5..c563851 100644
--- a/man/crypttab.xml
+++ b/man/crypttab.xml
@@ -305,14 +305,7 @@
listitemparaUse TrueCrypt in
In order to maximize consistency with newly committed options in
systemd-nspawn, would it make sense to allow independent configuration
of the process and file labels instead?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
Currently the user and session states are not stable, they are affected
by several races during login:
1) session state:
To get the session state the function session_get_state() is used.
Opening state:
At login the D-Bus CreateSession() method will call session_start() which
calls
The session_send_create_reply() function which notifies clients about
session creation is used for both session and user units. Unify the
shared code in a new function session_jobs_reply().
The session_save() will be called unconditionally on sessions since it
does not make sense to only call it
Summary:
Currently logind will not clear sessions on logout. The bug is confirmed
for getty and ssh logins. This series is preparation for next patches to
address that bug, it does not fix it.
However, this series also fixe real races on user and session states.
This ensures that user_save() and
To get the state of the session, the session_get_state() is used.
This function will check if the session-scope_job is set then it will
automatically return SESSION_OPENING. This is buggy in the context of
session closing:
At logout or D-Bus TerminateSession() fifo_fd is removed:
=
To get the state of the user, the user_get_state() is used.
This function will check if the user-slice_job or the user-service_job
are set then it will automatically return USER_OPENING. This is buggy
in the context of user closing:
At logout or D-Bus TerminateUser() calls user_stop()
user_stop()
match_job_removed() signal is triggered when queued jobs finish during
session opening or closing.
Calling session_jobs_reply() during opening is valid, but during
session closing does not make sense.
The session_send_create_reply() function which is called by
session_jobs_reply() is able to
On Thu, Feb 6, 2014 at 8:33 PM, Jan Janssen medhe...@web.de wrote:
---
man/crypttab.xml | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/man/crypttab.xml b/man/crypttab.xml
index 5f386e5..c563851 100644
--- a/man/crypttab.xml
+++ b/man/crypttab.xml
@@ -305,14
19 matches
Mail list logo
