Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=45511
---
src/service.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/src/service.c b/src/service.c
index 8b5c0b0..4bf6684 100644
--- a/src/service.c
+++ b/src/service.c
@@ -2208,9 +2208,10 @@ static void service_
On Mon, 19.03.12 09:42, David Ward ([email protected]) wrote:
> Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=45511
Sorry for not reviewing this more quickly!
Hmm, we probably should add a comment next to this line, explaining why
JOB_RESTART here, and not JOB_START, since this isn't o
On Fri, 30.03.12 17:20, Frederic Crozat ([email protected]) wrote:
> >From 5008080dda662208278c159213adbd5211496043 Mon Sep 17 00:00:00 2001
> From: Frederic Crozat
> Date: Thu, 29 Mar 2012 17:53:41 +0200
> Subject: [PATCH 1/2] macro: add newdup macro, equivalent of new + memdup but
> type-safe
>
On Fri, 30.03.12 18:26, Gustav Paul ([email protected]) wrote:
> Hello,
>
> I'm debugging a systemd shutdown problem where systemd hangs. I would like
> to track the shutdown process - presumably using log_error() all over the
> place.
>
> What is the best-practices development cycle for tes
On Thu, 29.03.12 18:58, Albert Strasheim ([email protected]) wrote:
> Hello all
>
> We have a problem with machines running systemd-37-15.fc16.x86_64
> hanging on reboot.
>
> We have a system that boots from an initramfs based on F16. Nothing
> much more special than yum --installroot and making
On Mon, 02.04.12 11:08, Colin Guthrie ([email protected]) wrote:
> This is just a nicer message than a python traceback.
Thanks!
Applied.
> ---
> src/systemd-analyze |4
> 1 file changed, 4 insertions(+)
>
> diff --git a/src/systemd-analyze b/src/systemd-analyze
> index 8148bfb..a49f
On Mon, 02.04.12 09:08, Dave Reisner ([email protected]) wrote:
> Fixes 'systemctl list-unit-files', which previously returned only:
>
> Failed to issue method call: No such file or directory
Thanks! Applied!
Lennart
--
Lennart Poettering - Red Hat, Inc.
___
'Twas brillig, and Colin Guthrie at 02/04/12 14:56 did gyre and gimble:
> 'Twas brillig, and Michal Schmidt at 02/04/12 14:47 did gyre and gimble:
>> Colin Guthrie wrote:
>>> So in this situation, as systemd is aiming for network.target, but
>>> it's not actually reached it yet, systemctl condresta
Lennart,
Thanks for your timely and informative replies. All is much clearer
now that I have found the documentation :-[
Dave.
On 04/02/2012 09:49 AM, Lennart Poettering wrote:
On Fri, 30.03.12 11:55, David Lambert ([email protected]) wrote:
Lennart,
I think I found another clue. I
On Fri, 30.03.12 11:55, David Lambert ([email protected]) wrote:
> Lennart,
> I think I found another clue. I noticed that the directory
> /var/log/journal was being used in addition to /var/run/log/journal.
> I do not want persistent logging, so I removed /var/log/journal.
> When I did this, s
On Thu, 29.03.12 15:42, David Lambert ([email protected]) wrote:
> Thanks Lennart, it looks like your guess was spot on! See attached
> trace. Any suggestions on how to narrow this down further?
So, this is probably simply because we try to map 128M of each journal
file by default, which is not mu
Sorry for dropping the list...
On Apr 2, 2012 4:04 PM, "Colin Guthrie" wrote:
>
> 'Twas brillig, and Tom Gundersen at 02/04/12 14:51 did gyre and gimble:
> >> > In our discussions, I was concerned that remote-fs.target was a
> >> > pre-requisite of systemd-user-sessions.service as on my machine,
'Twas brillig, and Michal Schmidt at 02/04/12 14:47 did gyre and gimble:
> Colin Guthrie wrote:
>> So in this situation, as systemd is aiming for network.target, but
>> it's not actually reached it yet, systemctl condrestart nscd appears to
>> hang, presumably waiting for network.target to be reach
Colin Guthrie wrote:
> So in this situation, as systemd is aiming for network.target, but
> it's not actually reached it yet, systemctl condrestart nscd appears to
> hang, presumably waiting for network.target to be reached (as nscd.service
> is ordered After network.target).
Does reverting commit
Hi,
Figured I'd send this as I discovered a deadlock on boot (resulting in
timeouts) that could potentially affect other distros too.
It relates to this:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/backends/NetworkManagerRedHat.c
(I've highlighted the RedHat one here, but
Fixes 'systemctl list-unit-files', which previously returned only:
Failed to issue method call: No such file or directory
---
src/install.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/install.c b/src/install.c
index 174d79b..9256116 100644
--- a/src/install.c
+++
On Mon, Apr 02, 2012 at 02:31:05PM +0200, Kay Sievers wrote:
> On Mon, Apr 2, 2012 at 14:22, Dave Reisner wrote:
> > Fixes 'systemctl list-unit-files', which previously returned only:
> >
> > Failed to issue method call: No such file or directory
> > ---
> > src/install.c | 2 +-
> > 1 file c
On Mon, Apr 2, 2012 at 14:22, Dave Reisner wrote:
> Fixes 'systemctl list-unit-files', which previously returned only:
>
> Failed to issue method call: No such file or directory
> ---
> src/install.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/install.c b/src/
Fixes 'systemctl list-unit-files', which previously returned only:
Failed to issue method call: No such file or directory
---
src/install.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/install.c b/src/install.c
index 174d79b..a7efc2a 100644
--- a/src/install.c
+++
Previously, systemd-user-sessions.service started after remote-fs.target.
If the user had any NFS mounts defined, this prevented logins until these
were processed.
If the user was using NFS for their home directories, this configuration
makes sense, but equally, the user may have remote mounts def
Hi,
I discussed this with Lennart the other day, but here is a followup
patch.
In our discussions, I was concerned that remote-fs.target was a
pre-requisite of systemd-user-sessions.service as on my machine, my
/mnt/scratch NFS mount delayed the display manager startup when it has
absolutely noth
This is just a nicer message than a python traceback.
---
src/systemd-analyze |4
1 file changed, 4 insertions(+)
diff --git a/src/systemd-analyze b/src/systemd-analyze
index 8148bfb..a49fbb7 100755
--- a/src/systemd-analyze
+++ b/src/systemd-analyze
@@ -31,6 +31,10 @@ def acquire_start_
22 matches
Mail list logo
