On Tue, Dec 17, 2013 at 07:41:59PM +0100, Djalal Harouni wrote:
> The following patches try to fix a regression in the loginctl --property
> logic and improve the code.
>
> [Patch 1/4] loginctl: replace strv_append() by strv_extend()
> [Patch 2/4] loginctl: add show_properties() to get login1 prop
Applied.
Zbyszek
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Tue, Dec 17, 2013 at 07:40:02PM -0500, Jason St. John wrote:
> In journalctl(1), be more explicit about the reference to "Seal=" in
> journald.conf(5) and what information can be found there.
> ---
> It took a decent amount of searching to find the actual peer refereed
> conference
> paper that
On Tue, Dec 17, 2013 at 06:48:43PM -0500, Jason St. John wrote:
> It may not be immediately obvious to the reader what "ID128" is, so replace
> the
> example option argument "ID128" with "128-bit-ID".
Applied.
Zbyszek
___
systemd-devel mailing list
syst
On Tue, Dec 17, 2013 at 09:36:28PM -0500, Jason St. John wrote:
> It's difficult to read the --help text when there are no indents for
> line-wrapped descriptions, so add indenting to provide a visual cue.
> ---
> I used an eight-space indent to match the coding style for systemd. If this is
> too
On Wed, Dec 18, 2013 at 05:40:55PM +0100, Holger Winkelmann [TP] wrote:
> Hi,
>
> We have just released the Erlang Binding ejournald [1] for the journal. It
> exposes the journal native
> API to log natively and query the journal.
>
> There is also a Erlang lager_journald_backend [2] which can
Hi David,
- Original Message -
> On Wed, Dec 18, 2013 at 10:32 AM, Holger Winkelmann [TP]
> wrote:
> > with HTTP you need to setup another server and provide a "Call back URL"
>
> Folks seem to increasingly call this pattern "web hooks."
I know, but i tried to avoid to use the webish te
It seems odd to combine Type=oneshot with Accept=false (which is the
default for socket activation). The latter setting causes systemd to
expect a persistent daemon to accept() connections.
___
systemd-devel mailing list
[email protected]
I replied in the thread with a subject line.
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Wed, Dec 18, 2013 at 10:32 AM, Holger Winkelmann [TP]
wrote:
> with HTTP you need to setup another server and provide a "Call back URL"
Folks seem to increasingly call this pattern "web hooks."
___
systemd-devel mailing list
[email protected]
On Wed, 18.12.13 13:32, Lukasz Skalski ([email protected]) wrote:
Thanks!
Applied!
> Flags for a name entry (KDBUS_NAME_*) should be set for
> cmd_name->flags (not conn_flags)
> ---
> src/bus-driverd/bus-driverd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --g
Hi,
- Original Message -
> On Wed, Dec 18, 2013 at 05:22:48PM +0100, Holger Winkelmann [TP] wrote:
> > means to send a message over HTTP which ends up in the journal, basically
> > the counterpart
> > of systems-journal.gatewayd?
> Yes.
cool, I'm not sooo sure about HTTP Transports works
On Wed, 18.12.13 15:30, Dr. Werner Fink ([email protected]) wrote:
> > Anyway, I suggested in my original reply that I'd be happy to merge a
> > patch that downgrades the warning message to debug on ENOENT. I have now
> > made such a change in git, and also added another change that closes
> > /dev/k
Hello.
I tried to execute a process by using socket activation.
As it is referred at systemd manual, I made "server" and "client" process
by using "sd-daemon.h" and "sd-daemon.c".
when I made those processes, I used UDS(Unix Domain Socket) to make
communication between server and client.
(I also m
Hello.
I tried to execute a process by using socket activation.
As it is referred at systemd manual, I made "server" and "client" process
by using "sd-daemon.h" and "sd-daemon.c".
when I made those processes, I used UDS(Unix Domain Socket) to make
communication between server and client.
(I also m
On Wed, Dec 18, 2013 at 05:22:48PM +0100, Holger Winkelmann [TP] wrote:
> means to send a message over HTTP which ends up in the journal, basically the
> counterpart
> of systems-journal.gatewayd?
Yes.
> What do think is the best transport representation for
> remote logging:
>
> a) keep the bin
Hi,
We have just released the Erlang Binding ejournald [1] for the journal. It
exposes the journal native
API to log natively and query the journal.
There is also a Erlang lager_journald_backend [2] which can be used for Erlang
applications.
[1] https://github.com/travelping/ejournald
[2] htt
Hi
> > By writing distributed applications we will look further for log
> > aggregation in the style of the systems-journal-gateway.
> > Regarding this I would like to know about the idea and plans of
> > the systemd community. Following the emails about logger optimization
> > Lennart mentioned
В Wed, 18 Dec 2013 02:52:01 +0100
Kay Sievers пишет:
> On Tue, Dec 17, 2013 at 8:14 PM, Andrey Borzenkov wrote:
> > В Tue, 17 Dec 2013 19:59:47 +0100 Kay Sievers пишет:
>
> >> # modprobe dummy
> >
> > dummy is not renamed.
>
> > UDEV [80256.274447] move /devices/pci:00/:00:03.0/n
В Wed, 18 Dec 2013 13:36:52 +0100
Robert Milasan пишет:
>
> So basically it doesn't really work ?!
>
It does not always work for net device as it looks like.
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.
On Wed, Dec 18, 2013 at 08:44:36AM +0100, Holger Winkelmann [TP] wrote:
> Hi all,
>
> we are following the discussion initiated by Cecil about systemd
> journal for a while. The last couple of weeks we have developed
> a Erlang adapter for the journal to allow structured native logging.
> Therefor
On Tue, Dec 17, 2013 at 08:06:39PM +0100, Lennart Poettering wrote:
>
> But why? LXC should either provide a working /dev/kmsg or none at
> all. Providing something that doesn't work where we then have to check
> with a lot of code if they are playing games with us or not is not an
> option really
On Wed, 18 Dec 2013 14:39:57 +0100
"Kay Sievers" wrote:
> On Wed, Dec 18, 2013 at 2:07 PM, Robert Milasan
> wrote:
>
> > One more question: Where exactly is 'test_device' variable saved, I
> > mean physically? I suppose it should be in /run/udev/data or
> > something similar no?
>
> Yes, in th
On Wed, Dec 18, 2013 at 2:07 PM, Robert Milasan wrote:
> One more question: Where exactly is 'test_device' variable saved, I
> mean physically? I suppose it should be in /run/udev/data or something
> similar no?
Yes, in the udev database at /run/udev/data/.
It's plain text, just look into it. T
On Wed, Dec 18, 2013 at 11:58:47AM +0100, Davide Bettio wrote:
> Hello,
>
> According to README minimum required kernel version for systemd 187 is
> 2.6.39, can anyone point me which features from that kernel version are
> required from systemd 187?
>
> I've been testing systemd 187 on 2.6.35 (
Hello,
On 18/12/2013 13:21, Kay Sievers wrote:
Devtmpfs fixes in the kernel, If I remember that correctly.
Do you think that 201 should work fine on top 2.6.35 like 187 used to?
I'm thinking about updating to that version without introducing any
possible regression.
Thank you for your previo
On Wed, 18 Dec 2013 02:52:01 +0100
"Kay Sievers" wrote:
> On Tue, Dec 17, 2013 at 8:14 PM, Andrey Borzenkov
> wrote:
> > В Tue, 17 Dec 2013 19:59:47 +0100 Kay Sievers пишет:
>
> >> # modprobe dummy
> >
> > dummy is not renamed.
>
> > UDEV [80256.274447]
> > move /devices/pci:00/:
On Tue, 17 Dec 2013 23:14:12 +0400
"Andrey Borzenkov" wrote:
> В Tue, 17 Dec 2013 19:59:47 +0100
> Kay Sievers пишет:
>
> >
> > Works just fine here as expected, it's probably something in your
> > setup.
> >
>
> No, it *your* default interface renaming :)
>
> > Kay
> >
> > # head -2 /etc/
Flags for a name entry (KDBUS_NAME_*) should be set for
cmd_name->flags (not conn_flags)
---
src/bus-driverd/bus-driverd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/bus-driverd/bus-driverd.c b/src/bus-driverd/bus-driverd.c
index b11eb55..f28dc57 100644
--- a/src/bus-d
On Wed, Dec 18, 2013 at 11:58 AM, Davide Bettio
wrote:
> According to README minimum required kernel version for systemd 187 is
> 2.6.39, can anyone point me which features from that kernel version are
> required from systemd 187?
Devtmpfs fixes in the kernel, If I remember that correctly.
Kay
_
Hello,
According to README minimum required kernel version for systemd 187 is
2.6.39, can anyone point me which features from that kernel version are
required from systemd 187?
I've been testing systemd 187 on 2.6.35 (on ARM) and it seemed to me
rather stable, I've also checked git log which
On Sun, Dec 15, 2013 at 12:06 PM, Thomas Bächler 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/login/logind-us
32 matches
Mail list logo