If Distribute=n, turns SO_REUSEPORT on, and spawns
n workers to handling incoming requests.
SO_REUSEPORT sockets on the same port must all be created
by the same uid, therefore using the option allows
other root programs (or programs of the same user
if running in --user mode) to "hijack" this por
On 12/13/13 at 06:42am, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Dec 13, 2013 at 01:33:17PM +0800, WANG Chao wrote:
> > Hi,
> >
> > In kdump environment, memory resource is quite limited. I find that the
> > runtime journal file (/run/log/journal/$id/system.journal) is 4 MB and I
> > think tha
On Fri, Dec 13, 2013 at 01:33:17PM +0800, WANG Chao wrote:
> Hi,
>
> In kdump environment, memory resource is quite limited. I find that the
> runtime journal file (/run/log/journal/$id/system.journal) is 4 MB and I
> think that is too much for a initramfs context.
>
> After tuning both RuntimeMa
Hi,
In kdump environment, memory resource is quite limited. I find that the
runtime journal file (/run/log/journal/$id/system.journal) is 4 MB and I
think that is too much for a initramfs context.
After tuning both RuntimeMaxUse=1% or RuntimeMaxFileSiz=100K, I find
system.journal is still 4 MB in
On Thu, Dec 12, 2013 at 09:51:43AM +0200, Joonas Lahtinen wrote:
> Hi Greg,
>
> I sent another set of patches, this time from command line, and at least
> I do not observe any line-wrapping with them when viewing the e-mail
> source. Did they apply fine for you?
Yes, it looked fine, I didn't tr
On Thu, Dec 12, 2013 at 8:15 AM, Kay Sievers wrote:
> We must not give the impression that this is "secure" in any way, it
> is not, and cannot generally be used unless it is secured by other
> things. So, no this is not secure at all, just possibly encrypted, but
> I doubt that was the question.
On Thu, Dec 12, 2013 at 11:02 AM, Lennart Poettering
wrote:
> On Thu, 12.12.13 10:00, Shawn Landden (sh...@churchofgit.com) wrote:
>
>
> Applied. Dropped the fflush(stderr) bits though as we that's not
> necessary for stderr, and not even for stdout if an \n was printed
> anyway...
ok, I was worri
On Wed, Dec 11, 2013 at 8:36 PM, Andrey Borzenkov wrote:
> This completely changes semantic of what it does. In this case no
> symlink is needed in the first place - just
> "touch .../unit.wants/other.unit" would be enough, as long as we assume
> units can only be located in standard config paths.
On Thu, Dec 12, 2013 at 6:23 AM, Lennart Poettering
wrote:
> This isn't right. Units might be symlinked under different names, we
> need to support that. For example, all template instances carry a
> different name for the symlink then for the source.
Good point, though we could still support tha
On Thu, 12.12.13 10:00, Shawn Landden (sh...@churchofgit.com) wrote:
Applied. Dropped the fflush(stderr) bits though as we that's not
necessary for stderr, and not even for stdout if an \n was printed
anyway...
Thanks!
>
> diff --git a/src/timedate/timedatectl.c b/src/timedate/timedatectl.c
>
On Thu, Dec 12, 2013 at 6:59 PM, Lennart Poettering
wrote:
> On Thu, 12.12.13 15:22, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
>
>> On 12/12/13 14:28, Lennart Poettering wrote:
>> > kay and Daniel are working on changing the semantics of monitoring
>> > entirely. Instead of turning mo
On Thu, 12.12.13 16:28, Marcel Holtmann (mar...@holtmann.org) wrote:
>
> Hi Lennart,
>
> >> why do we have to spawn threads or do forks for DNS. This looks all
> >> pretty expensive. In ConnMan for example we just wrote our own async
> >> DNS using a mainloop. Works perfectly fine an
On Thu, 12.12.13 17:42, Karol Lewandowski (lmc...@gmail.com) wrote:
> > Hmm, but this wouldn't be any different from old syslog, right? I mean,
> > old syslog also uses sendv() and recv() on AF_UNIX SOCK_DGRAM sockets...
>
> That's true, however, we aren't migrating from syslog, but from
> Androi
Which does have TimeUSec. Should we specifically check for this method
instead of assuming time=0 means it doesn't exist?
Before:
shawn@debian-T61:~/git/systemd$ ./timedatectl
Local time: Wed 1969-12-31 16:00:00 PST
Universal time: Thu 1970-01-01 00:00:00 UTC
RTC time: n/a
On Thu, 12.12.13 15:22, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
> On 12/12/13 14:28, Lennart Poettering wrote:
> > kay and Daniel are working on changing the semantics of monitoring
> > entirely. Instead of turning monitoring on and off on an existing
> > connection they want this t
On Thu, Dec 12, 2013 at 02:41:45PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Dec 12, 2013 at 02:00:48PM +0100, Marcel Holtmann wrote:
> > instead of moving everything around after the fact, I would say we better
> > start off with a clean patch set and everything in the right spot in the
On Thu, Dec 12, 2013 at 03:51:05PM +0100, Lennart Poettering wrote:
> On Thu, 12.12.13 14:12, Karol Lewandowski (k.lewando...@samsung.com) wrote:
(OP here from private email.)
> > Folks,
> >
> > We are trying to apply journald as default (and only) logging system
> > for our ARM-based handhelds.
On Thu, Dec 12, 2013 at 3:08 PM, Lennart Poettering
wrote:
> On Thu, 12.12.13 05:20, Kay Sievers (k...@vrfy.org) wrote:
>
>>
>> On Wed, Dec 11, 2013 at 11:53 PM, Reindl Harald
>> wrote:
>> > Am 11.12.2013 22:41, schrieb Cecil Westerhof:
>> >> I tried out systemd-journal-gatewayd. But it looks li
On 12/12/2013 04:22 PM, Simon McVittie wrote:
On 12/12/13 14:28, Lennart Poettering wrote:
kay and Daniel are working on changing the semantics of monitoring
entirely. Instead of turning monitoring on and off on an existing
connection they want this to be an entirely new connection type
Colin
On 12/12/2013 03:43 PM, Lennart Poettering wrote:
What I mend was the following:
As I understood it, there are Virtual Machine solutions that are
implemented as a service.
When there are several VM's running in this service and one of those
should get a lot more from the processor as the rest, th
Hi Lennart,
>> why do we have to spawn threads or do forks for DNS. This looks all
>> pretty expensive. In ConnMan for example we just wrote our own async
>> DNS using a mainloop. Works perfectly fine and is dirt cheap.
>
> Well, we don't fork threads/processes for each call b
On 12/12/13 14:28, Lennart Poettering wrote:
> kay and Daniel are working on changing the semantics of monitoring
> entirely. Instead of turning monitoring on and off on an existing
> connection they want this to be an entirely new connection type
Colin Walters wanted to do this in dbus-daemon too
Hi
On Thu, Dec 12, 2013 at 3:55 PM, Lennart Poettering
wrote:
> On Wed, 11.12.13 15:57, David Herrmann (dh.herrm...@gmail.com) wrote:
>
>>
>> Hey
>>
>> On Wed, Dec 11, 2013 at 3:27 PM, Lennart Poettering
>> wrote:
>> > On Wed, 11.12.13 13:54, David Herrmann (dh.herrm...@gmail.com) wrote:
>> >
>>
On Wed, 11.12.13 15:57, David Herrmann (dh.herrm...@gmail.com) wrote:
>
> Hey
>
> On Wed, Dec 11, 2013 at 3:27 PM, Lennart Poettering
> wrote:
> > On Wed, 11.12.13 13:54, David Herrmann (dh.herrm...@gmail.com) wrote:
> >
> >>
> >> Hi
> >>
> >> On Wed, Dec 11, 2013 at 12:18 AM, Lennart Poetterin
On Thu, 12.12.13 14:12, Karol Lewandowski (k.lewando...@samsung.com) wrote:
> Folks,
>
> We are trying to apply journald as default (and only) logging system
> for our ARM-based handhelds. There is one major problem, though -
> performance.
>
> We have found that journald can consume considerab
Am 12.12.2013 15:38, schrieb Lennart Poettering:
> On Wed, 11.12.13 19:56, Thomas Bächler (tho...@archlinux.org) wrote:
>
>> With the current logic, a user will never be garbage-collected, since its
>> manager will always be around. Change the logic such that a user is
>> garbage-collected when it
On Wed, 11.12.13 16:33, Cecil Westerhof (cecil.wester...@snow.nl) wrote:
>
> On 12/05/2013 08:39 PM, Lennart Poettering wrote:
> >>When virtual machines are implementd as a service. You need to let
> >>the host define the limits per guest I suppose?
> >
> >Not following?
> >
> >You can pack as ma
On Wed, 11.12.13 15:23, Lukasz Skalski (l.skal...@partner.samsung.com) wrote:
> log_assert_failed_return macro generates a lot of logs when we use
> bus_message_dump() function without checking masks in creds.
Actually, the checks in the creds object where wrong, they should not
have used assert_
On Thu, Dec 12, 2013 at 03:18:14PM +0100, Marcel Holtmann wrote:
> Hi Zbyszek,
>
> >> diff --git a/src/shared/logs-show.c b/src/shared/logs-show.c
> >> index c99fc7569429..0e3fd3de2630 100644
> >> --- a/src/shared/logs-show.c
> >> +++ b/src/shared/logs-show.c
> >> @@ -23,6 +23,7 @@
> >> #include
On Wed, 11.12.13 19:56, Thomas Bächler (tho...@archlinux.org) wrote:
> With the current logic, a user will never be garbage-collected, since its
> manager will always be around. Change the logic such that a user is
> garbage-collected when it has no sessions and linger is disabled.
> ---
> src/lo
On Wed, 11.12.13 14:04, Shawn Landden (sh...@churchofgit.com) wrote:
> Which does have TimeUSec. Should we specifically check for this method
> instead of assuming time=0 means it doesn't exist?
Sounds OK to just check against time == 0.
>
> +if (i->time)
For numeric values please alw
On Thu, 12.12.13 13:09, Lukasz Skalski (l.skal...@partner.samsung.com) wrote:
> Due to this patch, 'busctl monitor' prints all method calls,
> method errors and signals both for dbus and kdbus.
kay and Daniel are working on changing the semantics of monitoring
entirely. Instead of turning monitor
On Thu, 12.12.13 15:20, Marcel Holtmann (mar...@holtmann.org) wrote:
>
> Hi Andrey,
>
> why do we have to spawn threads or do forks for DNS. This looks all
> pretty expensive. In ConnMan for example we just wrote our own async
> DNS using a mainloop. Works perfectly fine and is di
On Wed, 11.12.13 15:54, da...@davidstrauss.net (da...@davidstrauss.net) wrote:
> From: David Strauss
>
> ---
> src/shared/install.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/src/shared/install.c b/src/shared/install.c
> index 17e8a75..14c0f4b 100644
> --- a/src/shared/insta
Hi Andrey,
why do we have to spawn threads or do forks for DNS. This looks all
pretty expensive. In ConnMan for example we just wrote our own async
DNS using a mainloop. Works perfectly fine and is dirt cheap.
>>>
>>> Well, we don't fork threads/processes for each call but reuse th
On Thu, 12.12.13 14:09, Marcel Holtmann (mar...@holtmann.org) wrote:
>
> Hi Lennart,
>
> >> why do we have to spawn threads or do forks for DNS. This looks all
> >> pretty expensive. In ConnMan for example we just wrote our own async
> >> DNS using a mainloop. Works perfectly fine and is dirt ch
Hi Zbyszek,
>> diff --git a/src/shared/logs-show.c b/src/shared/logs-show.c
>> index c99fc7569429..0e3fd3de2630 100644
>> --- a/src/shared/logs-show.c
>> +++ b/src/shared/logs-show.c
>> @@ -23,6 +23,7 @@
>> #include
>> #include
>> #include
>> +#include
>> #include
>> #include
>>
> Marc-Anto
On Thu, 12.12.13 05:20, Kay Sievers (k...@vrfy.org) wrote:
>
> On Wed, Dec 11, 2013 at 11:53 PM, Reindl Harald
> wrote:
> > Am 11.12.2013 22:41, schrieb Cecil Westerhof:
> >> I tried out systemd-journal-gatewayd. But it looks like that everyone that
> >> can
> >> contact, can get log info. Is
On Thu, Dec 12, 2013 at 05:17:27AM -0800, Marcel Holtmann wrote:
> diff --git a/src/shared/logs-show.c b/src/shared/logs-show.c
> index c99fc7569429..0e3fd3de2630 100644
> --- a/src/shared/logs-show.c
> +++ b/src/shared/logs-show.c
> @@ -23,6 +23,7 @@
> #include
> #include
> #include
> +#incl
On Thu, Dec 12, 2013 at 01:56:13PM +0900, Marc-Antoine Perennou wrote:
> Needed for socketpair, recv
> ---
> src/shared/logs-show.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/src/shared/logs-show.c b/src/shared/logs-show.c
> index c99fc75..0e3fd3d 100644
> --- a/src/shared/logs-show
В Thu, 12 Dec 2013 14:09:42 +0100
Marcel Holtmann пишет:
> Hi Lennart,
>
> >> why do we have to spawn threads or do forks for DNS. This looks all
> >> pretty expensive. In ConnMan for example we just wrote our own async
> >> DNS using a mainloop. Works perfectly fine and is dirt cheap.
> >
> >
On Thu, Dec 12, 2013 at 02:00:48PM +0100, Marcel Holtmann wrote:
> instead of moving everything around after the fact, I would say we better
> start off with a clean patch set and everything in the right spot in the
> first place.
Hi Marcel,
I have a local git-filter-tree-ed branch with the loca
CC src/shared/logs-show.lo
src/shared/logs-show.c: In function 'get_boot_id_for_machine':
src/shared/logs-show.c:1153:9: warning: implicit declaration of function
'socketpair' [-Wimplicit-function-declaration]
if (socketpair(AF_UNIX, SOCK_DGRAM, 0, sock) < 0)
^
src/shared
This commits extends journald with ability to pickup log snippets
from /dev/shm at configured time intervals (PickupIntervalSec).
First pickup is delayed by PickupStartupDelaySec.
This allows logging to be completely async, reducing number of
wakeups drastically under heavy load.
---
src/journal/
Enabled by default for test purposes.
---
src/journal/journal-send.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/src/journal/journal-send.c b/src/journal/journal-send.c
index 281e154..9c4acc2 100644
--- a/src/journal/journal-send.c
+++ b/src/journal
This is not a systemd patch but simple test program I have used
for measurements.
---
journal-feeder.c | 64
1 file changed, 64 insertions(+)
create mode 100644 journal-feeder.c
diff --git a/journal-feeder.c b/journal-feeder.c
new file mod
Folks,
We are trying to apply journald as default (and only) logging system
for our ARM-based handhelds. There is one major problem, though -
performance.
We have found that journald can consume considerable amount of CPU
time under moderate load (10-20% of CPU per, for say 100-300msg/s).
We h
Hi Lennart,
>> why do we have to spawn threads or do forks for DNS. This looks all
>> pretty expensive. In ConnMan for example we just wrote our own async
>> DNS using a mainloop. Works perfectly fine and is dirt cheap.
>
> Well, we don't fork threads/processes for each call but reuse them.
>
>
Hi Patrik,
> ---
> Makefile.am | 42 +-
> src/dhcp/Makefile |1 -
> src/dhcp/client.c | 1002 -
> src/dhcp/internal.h | 41 -
> src/dhcp/netwo
Hi Patrik,
>> I agree with Zbigniew: this should probably be in
>> src/libsystemd-dhcp/, so that this is similar to libsystemd-bus/,
>> libsystemd-id128/ and so on...
>
> Sent a patch for that, and in the process of creating an account on
> freedesktop.org. As that will most probably take some ti
Due to this patch, 'busctl monitor' prints all method calls,
method errors and signals both for dbus and kdbus.
---
src/libsystemd-bus/bus-control.c | 6 ++
src/libsystemd-bus/bus-match.c | 10 ++
src/libsystemd-bus/bus-match.h | 1 +
src/libsystemd-bus/busctl.c | 2 +-
4 f
I think my system had a bit older minor version of systemd (
systemd-204-8.fc19.x86_64 ). In another system I have tested where I have
systemd higher version - where the issue is not there - (
systemd-204-17.fc19.x86_64 ).
Thanks
Salil
On 11 December 2013 06:15, salil GK wrote:
> Thanks Lennar
On 12/12/2013 05:20 AM, Kay Sievers wrote:
On Wed, Dec 11, 2013 at 11:53 PM, Reindl Harald wrote:
Am 11.12.2013 22:41, schrieb Cecil Westerhof:
I tried out systemd-journal-gatewayd. But it looks like that everyone that can
contact, can get log info. Is that true, or am I overlooking something?
On Tue, 2013-12-10 at 18:48 +0100, Lennart Poettering wrote:
> I agree with Zbigniew: this should probably be in
> src/libsystemd-dhcp/, so that this is similar to libsystemd-bus/,
> libsystemd-id128/ and so on...
Sent a patch for that, and in the process of creating an account on
freedesktop.org.
54 matches
Mail list logo
