Op 11 apr. 2013, om 21:09 heeft David Strauss da...@davidstrauss.net het
volgende geschreven:
On Wed, Apr 10, 2013 at 11:00 PM, Koen Kooi k...@dominion.thruhere.net
wrote:
restarting it once it fails
Is it the socket or the service?
socket
___
2013/4/11 Koen Kooi k...@dominion.thruhere.net:
On Wed, Apr 10, 2013 at 11:00 PM, Koen Kooi k...@dominion.thruhere.net
wrote:
restarting it once it fails
Is it the socket or the service?
socket
I believe I experienced this with PHP-FPM when I injected the sockets
by abusing PHP-FPM's
On Mon, Apr 8, 2013 at 3:45 PM, Linda Walsh s...@tlinx.org wrote:
Is it something that systemd needed to have? I.e. if it is made
private would systemd care? If not, why would it have
been made shared?
Maybe a default in mount for root changed?
Having the default mount propagation be
Here is the commit with some background:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=b3ac5f8cb98757416d8660023d6564a7c411f0a0
On Thu, Apr 11, 2013 at 11:42 PM, David Strauss da...@davidstrauss.net wrote:
On Mon, Apr 8, 2013 at 3:45 PM, Linda Walsh s...@tlinx.org wrote:
Is it
I posted this to another, related thread, but here's the relevant
commit and reasoning:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=b3ac5f8cb98757416d8660023d6564a7c411f0a0
On Tue, Apr 9, 2013 at 5:15 AM, Tetsuo Handa
penguin-ker...@i-love.sakura.ne.jp wrote:
Andrey Borzenkov wrote:
From: Harald Hoyer har...@redhat.com
This patch series improves the argument handling of journalctl.
It ANDs all parameter like -b --unit= -p and multiple --unit= can be
specified.
The output of:
# journalctl -u sshd.service -u crond.service -u sshd.service -b -p 0..7
is now, what you would
From: Harald Hoyer har...@redhat.com
Previously only one --unit= or --user-unit could be specified.
With this patch, journalcrtl can show multiple units.
$ journalctl -u systemd-udevd.service -u sshd.service -u crond.service -b
-- Logs begin at Sa 2013-03-23 11:08:45 CET, end at Fr 2013-04-12
From: Harald Hoyer har...@redhat.com
cryptsetup itself has no timeout as default from the beginning. So the
default timeout has been 0 from the beginning.
https://bugzilla.redhat.com/show_bug.cgi?id=949702
---
src/cryptsetup/cryptsetup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Harald Hoyer har...@redhat.com
https://bugs.freedesktop.org/show_bug.cgi?id=63189
better fail than segfault
systemd[1]: Failed to load device unit: Invalid argument
systemd[1]: Failed to process udev device event: Invalid argument
---
src/core/device.c | 5 -
1 file changed, 4
foobar@.service and foobar@.service.d/myinstance.conf
foobar@.service and foobar@myinstance.service.d/myinstance.conf
This would be possible, if somebody implements it.
which don't work so I guess this isn't implemented. If so, would something
like that be a reasonable request to be
From: Harald Hoyer har...@redhat.com
https://bugs.freedesktop.org/show_bug.cgi?id=63189
better fail than segfault
systemd[1]: Failed to load device unit: Invalid argument
systemd[1]: Failed to process udev device event: Invalid argument
---
V2: Now checking for (r 0) rather than (r).
Thanks Kay for pointing me in the right direction
From fced3673ee1001dc905206f9a92ea2062f951d3c Mon Sep 17 00:00:00 2001
From: Robert Schweikert rjsch...@suse.com
Date: Fri, 12 Apr 2013 12:08:16 -0400
Subject: [PATCH] rules: add lid switch of ARM based Chromebook as a power
switch to logind
Hi,
In the python journal Reader, the splitting out of monotonic and
realtime stamps, has affected `get_next` function as timestamp values
are no longer present in the dictionary returned. Also the new
`get_monotonic` and `get_realtime` functions are not run through the
converters. Equally,
Op 12 apr. 2013, om 18:24 heeft Robert Schweikert rjsch...@suse.com het
volgende geschreven:
Thanks Kay for pointing me in the right direction
From fced3673ee1001dc905206f9a92ea2062f951d3c Mon Sep 17 00:00:00 2001
From: Robert Schweikert rjsch...@suse.com
Date: Fri, 12 Apr 2013 12:08:16
El 12/04/13 13:24, Robert Schweikert escribió:
Thanks Kay for pointing me in the right direction
From fced3673ee1001dc905206f9a92ea2062f951d3c Mon Sep 17 00:00:00 2001
From: Robert Schweikert rjsch...@suse.com
Date: Fri, 12 Apr 2013 12:08:16 -0400
Subject: [PATCH] rules: add lid switch of ARM
El 12/04/13 13:53, Stanislav Brabec escribió:
Add support for setting of initial state of NumLock. Supported values
are yes, no and bios (on x86 platforms).
It sets NumLock in virtual consoles. If NumLock should be turned on, it
also creates empty /run/numlock-on, which can be used e. g. for
Hi,
I'm having two issues in relation to the journal with my recent upgrade
to v201.
One issue, is that it appears that _MACHINE_ID field is missing the
= character. I had a quick look, and I think the bug was introduced on
the last part of the following commit:
El 12/04/13 13:53, Stanislav Brabec escribió:
Add support for setting of initial state of NumLock. Supported values
are yes, no and bios (on x86 platforms).
It sets NumLock in virtual consoles. If NumLock should be turned on, it
also creates empty /run/numlock-on, which can be used e. g. for
2013/4/12 Steven Hiscocks steven-syst...@hiscocks.me.uk
Hi,
I'm having two issues in relation to the journal with my recent upgrade to
v201.
One issue, is that it appears that _MACHINE_ID field is missing the =
character. I had a quick look, and I think the bug was introduced on the
last
On Sat, Apr 13, 2013 at 01:00:02AM +0200, Mirco Tischler wrote:
2013/4/12 Steven Hiscocks steven-syst...@hiscocks.me.uk
Hi,
I'm having two issues in relation to the journal with my recent upgrade to
v201.
One issue, is that it appears that _MACHINE_ID field is missing the =
---
src/journal/journald-server.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/journal/journald-server.c b/src/journal/journald-server.c
index 53e3830..be84323 100644
--- a/src/journal/journald-server.c
+++ b/src/journal/journald-server.c
@@ -538,7 +538,7 @@ static
On 13/04/13 00:00, Mirco Tischler wrote:
2013/4/12 Steven Hiscocks steven-syst...@hiscocks.me.uk
mailto:steven-syst...@hiscocks.me.uk
Hi,
I'm having two issues in relation to the journal with my recent
upgrade to v201.
One issue, is that it appears that _MACHINE_ID field is
On Sat, Apr 13, 2013 at 01:03:49AM +0200, Mirco Tischler wrote:
---
src/journal/journald-server.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Applied!
Zbyszek
diff --git a/src/journal/journald-server.c b/src/journal/journald-server.c
index 53e3830..be84323 100644
---
2013/4/13 Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl
On Sat, Apr 13, 2013 at 01:00:02AM +0200, Mirco Tischler wrote:
2013/4/12 Steven Hiscocks steven-syst...@hiscocks.me.uk
Hi,
I'm having two issues in relation to the journal with my recent upgrade to
v201.
One issue, is
On Fri, Apr 05, 2013 at 07:16:59PM +0200, Lennart Poettering wrote:
On Wed, 03.04.13 23:12, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
So, consider adding some form of numbering to the list of listen
addresses. Perhaps something like:
0: ListenStream:
On Fri, Apr 12, 2013 at 10:58 PM, Cristian Rodríguez crrodrig...@opensuse.org
+SUBSYSTEM==input, KERNEL==event*, KERNELS==gpio-keys.8,
TAG+=power-switch
LABEL=power_switch_end
Hrmm.. I think we need a vendor/device check here too.. otherwise it will
trigger on other unrelated machines..
This tool reads modules.devname from the current kernel directory and outputs
the information.
For now only the tmpfiles.d(5) format is supported, but more could easily be
added in the future if there is a need.
When booting with systemd, the new tool is called at boot to instruct
On Sat, Apr 13, 2013 at 12:36 AM, Cristian Rodríguez
crrodrig...@opensuse.org wrote:
El 12/04/13 13:53, Stanislav Brabec escribió:
Add support for setting of initial state of NumLock. Supported values
are yes, no and bios (on x86 platforms).
It sets NumLock in virtual consoles. If NumLock
28 matches
Mail list logo
