Le 21/11/2014 12:08, Colin Guthrie a écrit :
Hello again!
Hey, trying to revive the topic :)
Didier Roche wrote on 18/11/14 15:40:
Le 18/11/2014 15:59, Colin Guthrie a écrit :
Hiya,
Hey,
Didier Roche wrote on 18/11/14 13:58:
This would be maybe a nice way for the admin to know what's
Hi Robert,
On Fri, Nov 28, 2014 at 8:57 AM, Robert Milasan rmila...@suse.com wrote:
Hello, since a while back, there was a commit (haven't found it)
commit 8cc3f8c0bcd23bb68166cb197a4c541d7621b19c
Author: Harald Hoyer har...@redhat.com
Date: Mon Mar 25 13:02:05 2013 +0100
udevd.c: set
On Fri, 28 Nov 2014 13:51:04 +0100
Tom Gundersen t...@jklm.no wrote:
Also the patch changes the logging level of 'maximum number of
children reached' to an error, this should be visible as an error
when the number has been reached.
I don't think an error is appropriate here (as nothing
On 28.11.2014 13:59, Robert Milasan wrote:
On Fri, 28 Nov 2014 13:51:04 +0100
Tom Gundersen t...@jklm.no wrote:
Also the patch changes the logging level of 'maximum number of
children reached' to an error, this should be visible as an error
when the number has been reached.
I don't think
On 28.11.2014 08:57, Robert Milasan wrote:
Hello, since a while back, there was a commit (haven't found it) which
limits the number of children/workers to 8 + num_cpu * 2, which in a
normal case like a 4 core/cpu machine is 16 children/workers.
This limit is way too low even for a single
On Fri, 28 Nov 2014 14:28:31 +0100
Harald Hoyer harald.ho...@gmail.com wrote:
I think what we are seeing here is, that module loading saturates the
udev workers here. So there are at least 16 modprobes (kmod) running
and this hinders further processing of the uevents.
In theory we could
The handling of a service with KillMode set to something other than cgroup
is a bit confusing (as of systemd 208).
Suppose I have a service which has KillMode set to process and it happens
to leave some children behind.
# systemctl start tester
# systemctl status tester
tester.service - tester
Hey Gergely,
Gergely Nagy [2014-11-26 13:07 +0100]:
Forwarding is enabled by default on Debian, as I wrote in my
original mail. I have no control over the default, and I have no
desire to argue for changing it.
I'm just packaging systemd 217, and will revert the disabled
forwarding by default
On 28.11.2014 14:09, Harald Hoyer wrote:
On 28.11.2014 13:59, Robert Milasan wrote:
On Fri, 28 Nov 2014 13:51:04 +0100
Tom Gundersen t...@jklm.no wrote:
Also the patch changes the logging level of 'maximum number of
children reached' to an error, this should be visible as an error
when
Hello all,
while packaging 217 my integration tests for hostnamed yelled at me
that hostnamectl fails. Indeed it exits with 1 now even though it
succeeds.
Trivial patch attached. OK to push?
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer
Hi
On Fri, Nov 28, 2014 at 3:43 PM, Martin Pitt martin.p...@ubuntu.com wrote:
Hello all,
while packaging 217 my integration tests for hostnamed yelled at me
that hostnamectl fails. Indeed it exits with 1 now even though it
succeeds.
Trivial patch attached. OK to push?
Why not fix all
Am 28.11.2014 um 06:33 schrieb Martin Pitt:
Hello all,
Cameron Norman [2014-11-27 12:26 -0800]:
On Wed, Nov 26, 2014 at 1:29 PM, Richard Weinberger rich...@nod.at wrote:
Hi!
I run a Linux container setup with openSUSE 13.1/2 as guest distro.
After some time containers slow down.
An
Hey David,
David Herrmann [2014-11-28 15:49 +0100]:
Why not fix all those other occurrences with one fix by changing
hostnamectl_main() the last line from:
return r 0 ? EXIT_FAILURE : r;
to
return r 0 ? EXIT_FAILURE : 0;
Usually, =0 means success, 0 failure, in systemd. We
Choose which system users defined in sysusers.d/systemd.conf and files
or directories in tmpfiles.d/systemd.conf, should be provided depending
on comile-time configuration.
---
Makefile.am| 4
configure.ac | 2 ++
sysusers.d/.gitignore | 1 +
How does this interact with snapshots? While I was looking at man
systemctl it seems that one uses isolate to restore to a previous
snapshot:
Snapshot Commands
snapshot [NAME]
Create a snapshot. If a snapshot name is specified, the new
snapshot will be named after it. If
Hi
On Fri, Nov 28, 2014 at 3:54 PM, Martin Pitt martin.p...@ubuntu.com wrote:
Hey David,
David Herrmann [2014-11-28 15:49 +0100]:
Why not fix all those other occurrences with one fix by changing
hostnamectl_main() the last line from:
return r 0 ? EXIT_FAILURE : r;
to
return r 0
On Fri, Nov 28, 2014 at 10:40:31AM -0500, Chris Atkinson wrote:
I created a named snapshot:
$ sudo systemctl snapshot derpy
derpy.snapshot
I tried restoring the named snapshot, but the mandatory mangling
to .target got in the way:
$ sudo systemctl isolate derpy.snapshot
Failed to
The commit (5e03c6e3b517286bbd65b48d88f60e5b83721894) seems to be
having some side effects.
When I attempt to query status, stop or start a service I get
the following:
$ sudo systemctl stop transmission
Assertion 'suffix' failed at src/shared/unit-name.c:515, function
On Fri, Nov 28, 2014 at 01:09:18PM -0500, Chris Atkinson wrote:
The commit (5e03c6e3b517286bbd65b48d88f60e5b83721894) seems to be
having some side effects.
When I attempt to query status, stop or start a service I get
the following:
$ sudo systemctl stop transmission
Assertion 'suffix'
On Fri, 28.11.14 13:42, Ross Lagerwall (rosslagerw...@gmail.com) wrote:
The handling of a service with KillMode set to something other than cgroup
is a bit confusing (as of systemd 208).
Hmm, could you test this with newer systemd please? 208 is already
quite old.
Where (in terms of: which
Commit e80733be33e52d8ab2f1ae845326d39c600f5612 seems to have done the
trick.
I'm able to start, stop and status services, isolate .target
and .snapshot files and a filename with no extension following
isolate is treated as a .target, all of which seems right.
The systemctl man page will still
On Fri, Nov 28, 2014 at 02:02:24PM -0500, Chris Atkinson wrote:
Commit e80733be33e52d8ab2f1ae845326d39c600f5612 seems to have done the
trick.
I'm able to start, stop and status services, isolate .target
and .snapshot files and a filename with no extension following
isolate is treated as a
On Thu, Nov 27, 2014 at 07:21:55AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Nov 26, 2014 at 09:55:10PM -0800, Greg KH wrote:
On Thu, Nov 27, 2014 at 03:19:44PM +1000, Peter Hutterer wrote:
Currently a property in the form of
FOO=bar
is stored as FOO=bar, i.e. the property
On Thu, Nov 27, 2014 at 12:31:33PM +0100, Lennart Poettering wrote:
On Thu, 27.11.14 15:19, Peter Hutterer (peter.hutte...@who-t.net) wrote:
Currently a property in the form of
FOO=bar
is stored as FOO=bar, i.e. the property name contains a leading space.
That's quite hard to spot.
On Fri, Nov 28, 2014 at 07:53:33PM +0100, Lennart Poettering wrote:
On Fri, 28.11.14 13:42, Ross Lagerwall (rosslagerw...@gmail.com) wrote:
The handling of a service with KillMode set to something other than cgroup
is a bit confusing (as of systemd 208).
Hmm, could you test this with
On Fri, 28.11.14 20:50, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Sun, Nov 23, 2014 at 08:33:41PM -0800, Chris Leech wrote:
This adds auto detection for iSCSI and some FCoE drivers and treats
mounts to file-systems on those devices as remote-fs.
Signed-off-by: Chris
See
http://lists.freedesktop.org/archives/systemd-devel/2014-November/025644.html
et seq.
---
man/systemctl.xml | 12
src/systemctl/systemctl.c | 2 +-
2 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/man/systemctl.xml b/man/systemctl.xml
index
2014-10-29 16:22 GMT+01:00 Ronny Chevalier chevalier.ro...@gmail.com:
It helps editing units by either creating a drop-in file, like
/etc/systemd/system/my.service.d/override.conf, or by copying the
original unit from /usr/lib/systemd/ to /etc/systemd/ if the --full
option is specified.
It
On Fri, Nov 28, 2014 at 09:27:43PM +0100, Lennart Poettering wrote:
On Fri, 28.11.14 20:50, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Sun, Nov 23, 2014 at 08:33:41PM -0800, Chris Leech wrote:
This adds auto detection for iSCSI and some FCoE drivers and treats
mounts to
On Wed, Oct 29, 2014 at 04:22:02PM +0100, Ronny Chevalier wrote:
It helps editing units by either creating a drop-in file, like
/etc/systemd/system/my.service.d/override.conf, or by copying the
original unit from /usr/lib/systemd/ to /etc/systemd/ if the --full
option is specified.
It
On Fri, Nov 28, 2014 at 09:48:55PM +0100, Ronny Chevalier wrote:
2014-10-29 16:22 GMT+01:00 Ronny Chevalier chevalier.ro...@gmail.com:
It helps editing units by either creating a drop-in file, like
/etc/systemd/system/my.service.d/override.conf, or by copying the
original unit from
On Fri, Nov 28, 2014 at 03:37:25PM -0500, Chris Atkinson wrote:
See
http://lists.freedesktop.org/archives/systemd-devel/2014-November/025644.html
et seq.
Hi,
your patch is line-wrapper. Please resend it using git send-email
or as an attachment.
Zbyszek
Pid reuse is common, which means that it's difficult or impossible
to read information about a pid from /proc without races.
This introduces a second number associated with each (task, pidns)
pair called highpid. Highpid is a 64-bit number, and, barring
extremely unlikely circumstances or
[Adding CRIU people. Whoops.]
On Fri, Nov 28, 2014 at 3:05 PM, Andy Lutomirski l...@amacapital.net wrote:
Pid reuse is common, which means that it's difficult or impossible
to read information about a pid from /proc without races.
This introduces a second number associated with each (task,
On Wed, Nov 19, 2014 at 12:13:43AM +0900, WaLyong Cho wrote:
---
README | 3 +++
1 file changed, 3 insertions(+)
diff --git a/README b/README
index aefb349..70d1105 100644
--- a/README
+++ b/README
@@ -82,6 +82,9 @@ REQUIREMENTS:
CONFIG_CGROUP_SCHED
On Fri, Nov 28, 2014 at 03:05:01PM -0800, Andy Lutomirski wrote:
Pid reuse is common, which means that it's difficult or impossible
to read information about a pid from /proc without races.
This introduces a second number associated with each (task, pidns)
pair called highpid. Highpid is a
36 matches
Mail list logo
