Re: [systemd-devel] Regarding Journal crash patch

Thanks Susant! But it seems the function in which the patch you pointed to is applied is missing in systemd-219 source. So i may need to back port more patches in order to get around this issue. Thanks, Renjith On Mon, May 16, 2016 at 2:10 PM, Susant Sahani wrote: > >

Re: [systemd-devel] [networkd] dbus interface?

On Mon, May 16 2016, Lennart Poettering wrote: > That's actually the interface index formatted as integer > string. However, since D-Bus does not allow object path components to > start with a number it it is escaped with an underscored followed by > the ASCII code of the character... Hence "3"

Re: [systemd-devel] [networkd] dbus interface?

On Mon, 16.05.16 23:42, Yuri D'Elia (wav...@thregr.org) wrote: > On Mon, May 16 2016, Lennart Poettering wrote: > >> For example, the PropertyChanged signal might have a path of > >> "/org/freedesktop/network1/link/_33", however I have no clue what link > >> _33 actually refers to. > >> > >> In

Re: [systemd-devel] [networkd] dbus interface?

On Mon, May 16 2016, Lennart Poettering wrote: >> For example, the PropertyChanged signal might have a path of >> "/org/freedesktop/network1/link/_33", however I have no clue what link >> _33 actually refers to. >> >> In the node /org/freedesktop/network1/link/_33 there's nothing going >> back to

Re: [systemd-devel] [networkd] dbus interface?

On Mon, 16.05.16 21:30, Yuri D'Elia (wav...@thregr.org) wrote: > I'd like to monitor interface state changes as emitted by networkd. > > By monitoring the emitted signals though, it looks like the current > interface is either next to useless or I don't understand it at all. > > For example,

[systemd-devel] [networkd] dbus interface?

I'd like to monitor interface state changes as emitted by networkd. By monitoring the emitted signals though, it looks like the current interface is either next to useless or I don't understand it at all. For example, the PropertyChanged signal might have a path of

Re: [systemd-devel] network unit Match by router advertisement?

Lennart Poettering 2016-05-11 19:31: On Wed, 11.05.16 11:32, Brian Kroth (bpkr...@gmail.com) wrote: Hi again all, TL;DR: would it be possible (or make sense) to have systemd Match rules for network units that could match on some artifact of the network the link is

Re: [systemd-devel] default service restart action?

On May 11, 2016 12:07, "Lennart Poettering" wrote: > > On Wed, 11.05.16 11:27, Brian Kroth (bpkr...@gmail.com) wrote: > > > Hi all, I'm in the midst of steeping myself in systemd docs as I prepare to > > face lift a slew of services for Debian Jessie updates. > > > > As I

Re: [systemd-devel] Performing a config check before restarting a process

Terry Burton 2016-05-16 17:43: On 13 May 2016 at 00:04, Terry Burton wrote: I have a process (ISC DHCP) that has no reload or soft restart mechanism. The only way to "reload" it is a stop and start. I understand systemd's design choice of

Re: [systemd-devel] Performing a config check before restarting a process

On 13 May 2016 at 00:04, Terry Burton wrote: > I have a process (ISC DHCP) that has no reload or soft restart > mechanism. The only way to "reload" it is a stop and start. > > I understand systemd's design choice of maintaining a clear > distinction between reload and

Re: [systemd-devel] why are the systemd binaries so huge and can we do something about that?

On Mon, May 16, 2016 at 11:06 AM, Martin Pitt wrote: > Michael Biebl [2016-05-16 4:24 +0200]: >> Any ideas, why simple tools like loginctl, busctl, hostnamectl require 300K+ >> ? >> Could we move more common functionality into a shared, private library >> to counter the

Re: [systemd-devel] systemctl how to stop a service

Hello, Am Samstag, 14. Mai 2016, 16:55:11 CEST schrieb liuxueping: > I have a test in arm64,my test case try to start/stop a ntp service > frequently,like that: > > #!/bin/bash > i=0 > while [ 1 ];do > echo "$((i++))" > systemctl restart ntpd & > kill -9 $! You are

Re: [systemd-devel] why are the systemd binaries so huge and can we do something about that?

Am 16.05.2016 um 14:18 schrieb Michael Biebl: 2016-05-16 6:15 GMT+02:00 Auke Kok : On Mon, May 16, 2016 at 04:24:25AM +0200, Michael Biebl wrote: 1,5M usr/bin/systemd-analyze What's up with systemd-analyze? It shouldn't be part of a base package, it's not even a

Re: [systemd-devel] why are the systemd binaries so huge and can we do something about that?

2016-05-16 6:15 GMT+02:00 Auke Kok : > On Mon, May 16, 2016 at 04:24:25AM +0200, Michael Biebl wrote: >> 1,5M usr/bin/systemd-analyze >> >> What's up with systemd-analyze? > > It shouldn't be part of a base package, it's not even a diagnostic tool, more > like a

Re: [systemd-devel] systemctl how to stop a service

16.05.2016 13:28, Reindl Harald пишет: > > > Am 16.05.2016 um 08:58 schrieb Andrei Borzenkov: >> 16.05.2016 09:01, liuxueping пишет: >>> Do you mean to say that systemctl will return a value when the process >>> is still at terminate gracefully? >>> >> >> By default systemctl should wait for

Re: [systemd-devel] systemctl how to stop a service

Am 16.05.2016 um 08:58 schrieb Andrei Borzenkov: 16.05.2016 09:01, liuxueping пишет: Do you mean to say that systemctl will return a value when the process is still at terminate gracefully? By default systemctl should wait for stop job to complete. What may happen - if it takes more time

Re: [systemd-devel] why are the systemd binaries so huge and can we do something about that?

Michael Biebl [2016-05-16 4:24 +0200]: > Any ideas, why simple tools like loginctl, busctl, hostnamectl require 300K+ ? > Could we move more common functionality into a shared, private library > to counter the constant growth? Building src/shared/ into a private libsystemd-internal.so (which

Re: [systemd-devel] Regarding Journal crash patch

commit: https://github.com/systemd/systemd/commit/4de2402b603ea2f518f451d06f09e15aeae54fab Susant On Mon, May 16, 2016 at 12:05 PM, Renjith Vijayan wrote: > Hi, > > I am getting the exact journal service crash as mentioned in the link > below. > >

Re: [systemd-devel] systemctl how to stop a service

If it is as you say,it takes more time than JobTimeout,job is canceled while systemd is still trying to terminate unit,then the return value should not be 0. 在 2016/5/16 14:58, Andrei Borzenkov 写道: 16.05.2016 09:01, liuxueping пишет: Do you mean to say that systemctl will return a value

Re: [systemd-devel] autostart processes based on tty

Mantas Mikulėnas writes: > ~/.zprofile seems just fine for this task – it > *is* the zsh "run things on login" script after > all. (And since these are your personal processes, > especially the X stuff, it's much better to have > them running *inside* the login session along

Re: [systemd-devel] systemctl how to stop a service

16.05.2016 09:01, liuxueping пишет: > Do you mean to say that systemctl will return a value when the process > is still at terminate gracefully? > By default systemctl should wait for stop job to complete. What may happen - if it takes more time than JobTimeout, job is canceled while systemd is

[systemd-devel] Regarding Journal crash patch

Hi, I am getting the exact journal service crash as mentioned in the link below. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805042 (journal is killed every minute by watchdog) We are using systemd-219. This bug seems to be fixed in latest versions of systemd. We will not be able to

Re: [systemd-devel] systemctl how to stop a service

Do you mean to say that systemctl will return a value when the process is still at terminate gracefully? 在 2016/5/14 18:32, Reindl Harald 写道: Am 14.05.2016 um 10:55 schrieb liuxueping: The result of "ps aux" before sleep 5 shows: root 6698 0.0 0.0 0 0 ?Ds 08:45