Re: [systemd-devel] StartupFinished signal is not sent on 210

Hi On Tue, Mar 4, 2014 at 8:55 PM, Lennart Poettering lenn...@poettering.net wrote: On Tue, 04.03.14 14:12, Umut Tezduyar Lindskog (umut.tezdu...@axis.com) wrote: Hi, I have noticed systemd doesn't generate the StartupFinished dbus signal on 210 (probably 209 too). The code tells me we

Re: [systemd-devel] The Bridge on the River PID EINS

Hi, I tried out a similar configuration and couldn't get the bridge up. I tried it on Arch with systemd 210. bridge.netdev [NetDev] Name=bridge0 Kind=bridge u.network [NetDev] Name=bridge0 Kind=bridge Further debugging, seems like networkd never receives the RTM_NEWLINK for the bridge. Since

Re: [systemd-devel] The Bridge on the River PID EINS

On Mon, Mar 10, 2014 at 9:12 PM, Umut Tezduyar u...@tezduyar.com wrote: Hi, I tried out a similar configuration and couldn't get the bridge up. I tried it on Arch with systemd 210. bridge.netdev [NetDev] Name=bridge0 Kind=bridge u.network [NetDev] Name=bridge0 Kind=bridge Ops, copy

Re: [systemd-devel] [PATCH] timedated: add --timezone option to set the default timezone

Hi Juho, Isn't linking /etc/localtime to your custom file enough? On Mon, Mar 17, 2014 at 6:34 PM, Juho Son juho80@samsung.com wrote: This option could changes the default system's time zone. The default time zone is /etc/localtime. If we want to use the specific path, we could use this

Re: [systemd-devel] How to compute a value for a service argument or environment value?

Hi Alan, As Cristian has suggested, the correct behavior is letting daemons pick up the right argument. Though, there is a hack if you can't re implement the daemon. You could compute the variables in an ExecStartPre= and write them to a file (/run/yourservice/arg) and point your

Re: [systemd-devel] systemd read-only RootFS for flash-menory usage ?

Hi, Short answer is YES to your first question. For long answer, http://0pointer.de/blog/projects/stateless.html. Umut On Jul 19, 2014, at 5:04 PM, lux-integ lux-in...@btconnect.com wrote: Greetings, I have a computer with these --OS Linux 64bit BLFS Linux --relatively recent

[systemd-devel] journal and /run/systemd/journal/syslog

Hi, I have noticed that if journal fails to send messages to /run/systemd/journal/syslog, it increments a counter and every 30 seconds it prints out a message on journal informing that forwarding x many messages has failed. If journal storage is set to none, there is no way of being informed

Re: [systemd-devel] [PATCH] static-nodes: move creation of static nodes from udevd to tmpfiles

Hi Tom, Just a suggestion, can kmod-static-nodes.service be merged to systemd-static-nodes.service and have 2 ExecStartPre= as: ExecStartPre=/usr/bin/mkdir -p /run/tmpfiles.d ExecStartPre=/usr/bin/kmod static-nodes --format=tmpfiles --output=/run/tmpfiles.d/kmod.conf On Sun, Jul 7, 2013 at 4:15

Re: [systemd-devel] [PATCH] static-nodes: move creation of static nodes from udevd to tmpfiles

On Sun, Jul 7, 2013 at 11:17 PM, Tom Gundersen t...@jklm.no wrote: Hi Umut, On Sun, Jul 7, 2013 at 8:11 PM, Umut Tezduyar u...@tezduyar.com wrote: Just a suggestion, can kmod-static-nodes.service be merged to systemd-static-nodes.service and have 2 ExecStartPre= as: ExecStartPre=/usr/bin

[systemd-devel] [PATCH] core: notify triggered by socket of a service

--- systemd/src/core/service.c | 31 --- systemd/src/core/socket.c | 33 - systemd/src/core/socket.h |3 --- 3 files changed, 32 insertions(+), 35 deletions(-) diff --git a/src/core/service.c b/src/core/service.c index

Re: [systemd-devel] [PATCH] core: notify triggered by socket of a service

Hi, This patch is in reference to http://lists.freedesktop.org/archives/systemd-devel/2013-June/011405.html in case your mail client doesn't group it by the thread. I have tested it on systemd 204 but patch applies to 205 (not tested). Thanks On Wed, Jul 10, 2013 at 9:19 AM, Umut Tezduyar u

Re: [systemd-devel] journal and /run/systemd/journal/syslog

On Tue, Jul 9, 2013 at 1:58 AM, Lennart Poettering lenn...@poettering.net wrote: On Sun, 07.07.13 19:18, Umut Tezduyar (u...@tezduyar.com) wrote: Hi, I have noticed that if journal fails to send messages to /run/systemd/journal/syslog, it increments a counter and every 30 seconds it prints

Re: [systemd-devel] journal and /run/systemd/journal/syslog

On Wed, Jul 10, 2013 at 12:55 PM, Kay Sievers k...@vrfy.org wrote: On Wed, Jul 10, 2013 at 12:30 PM, Umut Tezduyar u...@tezduyar.com wrote: On Tue, Jul 9, 2013 at 1:58 AM, Lennart Poettering lenn...@poettering.net wrote: We though about just bumping this globally via sysctl, but we feared

Re: [systemd-devel] [PATCH] core: notify triggered by socket of a service

On Wed, Jul 10, 2013 at 9:19 AM, Umut Tezduyar u...@tezduyar.com wrote: --- systemd/src/core/service.c | 31 --- systemd/src/core/socket.c | 33 - systemd/src/core/socket.h |3 --- 3 files changed, 32 insertions(+), 35

Re: [systemd-devel] journal and /run/systemd/journal/syslog

On Fri, Jul 12, 2013 at 1:08 AM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 10.07.13 12:30, Umut Tezduyar (u...@tezduyar.com) wrote: We though about just bumping this globally via sysctl, but we feared that might not sit well with some folks, as we shouldn't change a global

Re: [systemd-devel] [PATCH] core: notify triggered by socket of a service

On Wed, Jul 10, 2013 at 2:24 PM, Umut Tezduyar u...@tezduyar.com wrote: On Wed, Jul 10, 2013 at 9:19 AM, Umut Tezduyar u...@tezduyar.com wrote: --- systemd/src/core/service.c | 31 --- systemd/src/core/socket.c | 33 - systemd

[systemd-devel] [PATCHv2] core: notify triggered by socket of a service

Refer to: http://lists.freedesktop.org/archives/systemd-devel/2013-June/011532.html --- TODO |3 --- src/core/service.c | 31 --- src/core/socket.c | 33 - src/core/socket.h |3 --- 4 files changed, 32

[systemd-devel] Has systemd booted up command

Hi, This is in reference to https://bugs.freedesktop.org/show_bug.cgi?id=66926 request. I have been polling systemd with systemctl is-active default.target to detect if boot up has been completed or not. I have noticed that this is not enough though. It seems like starting a service that is

Re: [systemd-devel] [PATCHv2] core: notify triggered by socket of a service

On Thu, Jul 18, 2013 at 3:27 AM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 17.07.13 09:46, Umut Tezduyar (u...@tezduyar.com) wrote: +static void socket_trigger_notify(Unit *u, Unit *other) { +Socket *s = SOCKET(u); +Service *se = SERVICE(other

[systemd-devel] [PATCHv3] core: notify triggered by socket of a service

Refer to: http://lists.freedesktop.org/archives/systemd-devel/2013-June/011532.html --- TODO |3 --- src/core/service.c | 31 --- src/core/socket.c | 34 +- src/core/socket.h |3 --- 4 files changed, 33

Re: [systemd-devel] Has systemd booted up command

On Thu, Jul 18, 2013 at 7:06 PM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 18.07.13 10:08, Umut Tezduyar (u...@tezduyar.com) wrote: Hi, This is in reference to https://bugs.freedesktop.org/show_bug.cgi?id=66926 request. I have been polling systemd with systemctl is-active

[systemd-devel] [PATCHv4] core: notify triggered by socket of a service

--- TODO |3 --- src/core/service.c | 31 --- src/core/socket.c | 39 ++- src/core/socket.h |3 --- 4 files changed, 38 insertions(+), 38 deletions(-) diff --git a/TODO b/TODO index ba8bb8e..e0c4857

Re: [systemd-devel] [PATCHv3] core: notify triggered by socket of a service

On Thu, Jul 18, 2013 at 8:11 PM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 18.07.13 15:27, Umut Tezduyar (u...@tezduyar.com) wrote: +static void socket_trigger_notify(Unit *u, Unit *other) { +Socket *s = SOCKET(u); +Service *se = SERVICE(other

[systemd-devel] Excluding .hwdb files

Hi, For an embedded system that is not using hwdb.bin, we are shipping roughly 4 mb .hwdb files under /usr/lib/udev/hwdb.d. Is it distributions responsibility to clean up .hwdb files after build or should we have a configure option to exclude hwdb support? Thanks, Umut

Re: [systemd-devel] [PATCHv4] core: notify triggered by socket of a service

Hi, any update on accepting this patch? Umut On Mon, Jul 22, 2013 at 10:52 AM, Umut Tezduyar u...@tezduyar.com wrote: --- TODO |3 --- src/core/service.c | 31 --- src/core/socket.c | 39 ++- src/core

[systemd-devel] Start and stop requests for a service

Hi, I have noticed that ExecStop is not being run on following service with following requests: [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/sh -c sleep 20 /usr/bin/systemd-cat echo ExecStart.. ExecStop=/bin/sh -c /usr/bin/systemd-cat echo ExecStop.. $ systemctl start

Re: [systemd-devel] Start and stop requests for a service

On Tue, Oct 1, 2013 at 3:51 AM, Lennart Poettering lenn...@poettering.net wrote: On Fri, 27.09.13 11:37, Umut Tezduyar (u...@tezduyar.com) wrote: Hi, I have noticed that ExecStop is not being run on following service with following requests: [Service] Type=oneshot RemainAfterExit=yes

Re: [systemd-devel] [PATCHv4] core: notify triggered by socket of a service

Hi, I haven't seen a delay on my boot but I was thinking maybe you can try to comment out following section to see if it will make any difference. +if (se-state == SERVICE_RUNNING) +socket_set_state(s, SOCKET_RUNNING); On Wed, Oct 2, 2013 at 12:50 PM, Colin Guthrie

[systemd-devel] journal on jffs2

Hi, This message is only for archiving purposes. I have noticed that journal is not persisting on jffs2 file system and my guess is it is due to missing mmap support of jffs2. I don't have an easy workaround other than: a) Making journal forwarding logs to a home grown daemon that writes

[systemd-devel] Where did DefaultControllers= option go?

Hi, I have noticed DefaultControllers= option is no longer in system.conf file. Has it been moved to somewhere else or are all controllers default controllers by default? If all the controllers are default controllers then something is weird. I have both cpu and cpuacct controllers (and they are

Re: [systemd-devel] Where did DefaultControllers= option go?

On Tue, Oct 29, 2013 at 5:52 PM, Kay Sievers k...@vrfy.org wrote: On Tue, Oct 29, 2013 at 5:39 PM, Thomas Bächler tho...@archlinux.org wrote: Am 29.10.2013 17:21, schrieb Colin Guthrie: 'Twas brillig, and Umut Tezduyar at 29/10/13 15:17 did gyre and gimble: I have noticed DefaultControllers

Re: [systemd-devel] Where did DefaultControllers= option go?

On Tue, Oct 29, 2013 at 6:56 PM, Kay Sievers k...@vrfy.org wrote: On Tue, Oct 29, 2013 at 6:45 PM, Umut Tezduyar u...@tezduyar.com wrote: The global mirroring across trees makes no sense in the future. The several independent trees will go away in the kernel next year, and then systemd would

Re: [systemd-devel] [PATCH 1/2] bus-util: add ssh and polkit connection methods

Hi, Speaking about ssh, are sd_bus_open_system_remote() and bus_connect_system_ssh() doing similar things? bus_connect_system_ssh expects the unixexec: support from dbus library. Can bus_connect_system_ssh be replaced with sd_bus_open_system_remote so we won't be dependent on latest (Seems like

Re: [systemd-devel] default dbus socket path being /run

On Tue, Dec 17, 2013 at 8:26 PM, Lennart Poettering lenn...@poettering.net wrote: On Tue, 17.12.13 20:23, Umut Tezduyar Lindskog (umut.tezdu...@axis.com) wrote: Hi, Now that dbus sockets are by default expected to be in /run by systemd; /var/run by other dbus libraries, we have to use env

Re: [systemd-devel] symbolic link for systemd-stdio-bridge

On Thu, Dec 19, 2013 at 5:34 PM, Umut Tezduyar Lindskog umut.tezdu...@axis.com wrote: It is broken when bindir is /usr/bin and /lib is not symbolic link to /usr/lib. bus-proxyd-install-hook: $(AM_V_LN)$(LN_S) -f ../../lib/systemd/systemd-bus-proxyd $(DESTDIR)$(bindir)/systemd-stdio

[systemd-devel] networkd: Loosing nic's driver set functionality

Hi Tom, Making RTM_GETLINK and RTM_SETLINK asynchronously is causing RTM_SETLINK to remove the nic's functionality. In my case, I am loosing IFF_MULTICAST after networkd sets the interface up. I am not sure if 5d4795f37229 can solve the problem but the only documentation I found was stating

Re: [systemd-devel] networkd: Loosing nic's driver set functionality

Hi Marcel, Tom, Thanks for the tips. Tom, I will try the git and let you know if it doesn't work but from the kernel code, it seems it should work fine. Thanks, Umut On Wed, Jan 22, 2014 at 8:08 PM, Marcel Holtmann mar...@holtmann.org wrote: Hi Umut, Making RTM_GETLINK and RTM_SETLINK

[systemd-devel] [PATCH] random-seed: Fix error message typo

The file node is /dev/urandom, not /dev/random. --- src/random-seed/random-seed.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/random-seed/random-seed.c b/src/random-seed/random-seed.c index c2729fe..1257c52 100644 --- a/src/random-seed/random-seed.c +++

[systemd-devel] [PATCH] Disable firmware loading when firmware file is 0 byte

If firmware file is not found in the file system, udev terminates firmware loading. This is not the case if firmware file exists in the file system but doesn't have any data in it. --- systemd/src/udev/udev-builtin-firmware.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git

[systemd-devel] [PATCH] systemctl: fix typo

--- shell-completion/systemd-zsh-completion.zsh |6 +++--- src/systemctl/systemctl.c |4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/shell-completion/systemd-zsh-completion.zsh b/shell-completion/systemd-zsh-completion.zsh index a58f4ae..93d64b3

[systemd-devel] [PATCH] Add missing bootchart manual and conf file

--- Makefile.am |5 - 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/Makefile.am b/Makefile.am index 474110a..2232a1d 100644 --- a/Makefile.am +++ b/Makefile.am @@ -3027,11 +3027,14 @@ systemd_bootchart_SOURCES = \ src/bootchart/svg.c MANPAGES += \ -

[systemd-devel] Starting a service on shutdown

Hi How do I start a service on shutdown that will start and finish before any of the mount points being unmounted? As it is explained here ( http://lists.freedesktop.org/archives/systemd-devel/2012-November/007558.html) the shutdown order is the reverse of startup order though it is not clear

[systemd-devel] [PATCH] core: Set source for mountinfo .mount units

--- src/core/mount.c |6 +- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/src/core/mount.c b/src/core/mount.c index 03eff9d..e5f5e42 100644 --- a/src/core/mount.c +++ b/src/core/mount.c @@ -1472,7 +1472,7 @@ static int mount_add_one( int r; Unit *u;

Re: [systemd-devel] [PATCH] core: Set source for mountinfo .mount units

Regardless of this patch, it might be a good idea to mention /proc/self/mountinfo in systemd.mount(5) as currently there is no mention of .mount files might pop up by systemd by looking at /proc/self/mountinfo. Thanks On Wed, Jan 23, 2013 at 9:23 AM, Umut Tezduyar u...@tezduyar.com wrote

[systemd-devel] [PATCH] man: remove boot up runlevel support

As of 3cdebc217c42c8529086f2965319b6a48eaaeabe support for distro specific boot up runlevels has been dropped. --- man/systemd.special.xml | 10 -- 1 files changed, 0 insertions(+), 10 deletions(-) diff --git a/man/systemd.special.xml b/man/systemd.special.xml index 6acba91..0d1df84

[systemd-devel] [PATCH 1/2] core: keep mountinfo .mounts until late shutdown

.mount units coming from /proc/self/mountinfo file are unmounted after local-fs.target is reached during shutdown. Problem: .mount units popping up in mountinfo file are added to systemd without any dependency. For that reason, they are the first one to be unmounted during shutdown. Whichever

[systemd-devel] [PATCH 2/2] core: do not overwrite existing units source

Only set source for freshly created .mounts coming from mountinfo file. --- src/core/mount.c | 12 +++- 1 files changed, 7 insertions(+), 5 deletions(-) diff --git a/src/core/mount.c b/src/core/mount.c index 29ce440..8231059 100644 --- a/src/core/mount.c +++ b/src/core/mount.c @@

Re: [systemd-devel] [PATCH 1/2] core: keep mountinfo .mounts until late shutdown

Downside of this patch is, mountinfo mounts stick around as inactive-dead even when the file system they represent is unmounted. On Mon, Feb 4, 2013 at 3:00 PM, Umut Tezduyar u...@tezduyar.com wrote: .mount units coming from /proc/self/mountinfo file are unmounted after local-fs.target

Re: [systemd-devel] [PATCH] [RFC] Remove installation of symlinks in /etc

Hi, If I am not mistaken, moving getty@tty1.service and remote-fs.target to $systemunitdir will cause them to be shown as disabled on systemctl status .unit even though they are enabled. These unit files have [Install] sections and when there is [Install] section on them, systemd will look for a

[systemd-devel] Can bootchart take advantage of startup completed signal?

Hi Auke, I was wondering if you have tried to take advantage of StartupFinished signal sent by systemd ( http://www.freedesktop.org/wiki/Software/systemd/dbus). Would it make sense to register on StartupFinished signal and stop taking measurements when systemd boots up completely? This would be

Re: [systemd-devel] [PATCH 1/2] core: keep mountinfo .mounts until late shutdown

on it. Sorry for the delay. Thanks On Mon, Mar 4, 2013 at 8:30 PM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Thu, Feb 14, 2013 at 09:15:28PM +0100, Zbigniew Jędrzejewski-Szmek wrote: On Mon, Feb 04, 2013 at 05:27:24PM +0100, Umut Tezduyar wrote: Hi On Mon, Feb 4

Re: [systemd-devel] [what-do-you-think? PATCH] man/*.html: link to directives and python in header

GREAT! One suggestion though, would it make sense to split the APIs from programs? Currently, S index is filled with APIs that most of the users only scroll. On Thu, Mar 7, 2013 at 7:25 PM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: --- Results look like

[systemd-devel] Ordering for early initialization services

Hi, What would be the advantage of placing an early boot up script in between local-fs.target/sysinit.target OR in between sysinit.target/basic.target? I cannot decide what should be the ordering for some early initialization oneshot services I have in my embedded system. These services makes

Re: [systemd-devel] Ordering for early initialization services

Maybe bandwith wasn't the best example :) But my question is still valid. On Fri, Mar 8, 2013 at 2:18 PM, Reindl Harald h.rei...@thelounge.netwrote: Am 08.03.2013 14:12, schrieb Umut Tezduyar: To summarize, where are users encouraged to place their early boot up initialization services

[systemd-devel] Why do stop jobs run asynchronously on systemctl isolate target?

Hi, I have realized that return of systemctl isolate target command is only synchronous for starting jobs but not for stopping jobs. How can one make sure when systemctl isolate target returns, services that are needed to be stopped are stopped AND services that are needed to be started are

Re: [systemd-devel] [PATCH] core: fix getting information about mount unit

Hi, I thought mounts coming from mountinfo are not getting default dependencies anyways. mount_add_one() never sets load_extras to true for new mount units. load_extras is the control to call mount_add_extras which will eventually call mount_add_default_dependencies(). Or I have replied to

[systemd-devel] [PATCH] Don't pull in sysctl on shutdown

No need to try to stop systemd-sysctl on shutdown as this service doesn't have ExecStop= anyways. --- units/systemd-sysctl.service.in |1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/units/systemd-sysctl.service.in b/units/systemd-sysctl.service.in index 45e1ceb..d914553

[systemd-devel] [PATCH] build-sys: configurable debug shell tty path

--- configure.ac |9 + units/debug-shell.service.in |4 ++-- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/configure.ac b/configure.ac index 28d7286..75bda8a 100644 --- a/configure.ac +++ b/configure.ac @@ -742,6 +742,15 @@ AS_IF([test

Re: [systemd-devel] Ordering for early initialization services

Hi, I would like to bring my discussion back. Any help? Thanks On Fri, Mar 8, 2013 at 2:12 PM, Umut Tezduyar u...@tezduyar.com wrote: Hi, What would be the advantage of placing an early boot up script in between local-fs.target/sysinit.target OR in between sysinit.target/basic.target? I

Re: [systemd-devel] Why do stop jobs run asynchronously on systemctl isolate target?

Hi, Can we bring this discussion up again please? Thank you. On Fri, Mar 8, 2013 at 2:38 PM, Umut Tezduyar u...@tezduyar.com wrote: Hi, I have realized that return of systemctl isolate target command is only synchronous for starting jobs but not for stopping jobs. How can one make sure

[systemd-devel] [PATCH 1/2] systemd-analyze: refactor for more data collection

--- src/analyze/systemd-analyze.c | 119 +++-- 1 files changed, 66 insertions(+), 53 deletions(-) diff --git a/src/analyze/systemd-analyze.c b/src/analyze/systemd-analyze.c index 01bf55e..3dcde30 100644 --- a/src/analyze/systemd-analyze.c +++

Re: [systemd-devel] Why do stop jobs run asynchronously on systemctl isolate target?

...@poettering.netwrote: On Fri, 08.03.13 14:38, Umut Tezduyar (u...@tezduyar.com) wrote: Hi, I have realized that return of systemctl isolate target command is only synchronous for starting jobs but not for stopping jobs. How can one Well, it is synchronous to jobs that are ordered against

Re: [systemd-devel] Ordering for early initialization services

Hi, My concern was being forward compatible with systemd and you have addressed my concern. Thank you. On Sat, Mar 23, 2013 at 3:55 AM, Lennart Poettering lenn...@poettering.netwrote: On Fri, 08.03.13 14:12, Umut Tezduyar (u...@tezduyar.com) wrote: Hi, What would be the advantage

Re: [systemd-devel] [PATCH 1/2] systemd-analyze: refactor for more data collection

Hi, Reason was for patch 2/2 as this is patch 1/2. Thanks. On Mon, Mar 25, 2013 at 9:32 PM, Kok, Auke-jan H auke-jan.h@intel.comwrote: On Sun, Mar 24, 2013 at 11:23 AM, Umut Tezduyar u...@tezduyar.com wrote: --- src/analyze/systemd-analyze.c | 119

Re: [systemd-devel] [PATCH 2/2] systemd-analyze: --type cpuacct option for blame

, Mar 25, 2013 at 9:59 PM, Kok, Auke-jan H auke-jan.h@intel.comwrote: On Sun, Mar 24, 2013 at 11:23 AM, Umut Tezduyar u...@tezduyar.com wrote: systemd-analyze blame --type cpuacct displays cpu time usage information of the cgroup. The information displayed is cpuacct.usage

[systemd-devel] [PATCH] cgtop: Add cpu time opt and become stdout sensitive

--- src/cgtop/cgtop.c | 108 - 1 files changed, 74 insertions(+), 34 deletions(-) diff --git a/src/cgtop/cgtop.c b/src/cgtop/cgtop.c index eebebf0..0ef4fcc 100644 --- a/src/cgtop/cgtop.c +++ b/src/cgtop/cgtop.c @@ -69,6 +69,11 @@ static enum {

Re: [systemd-devel] [PATCH] cgtop: Add cpu time opt and become stdout sensitive

Hi Zbigniew, Thank you very much for reviewing. Please find my comments below. On Mon, Apr 1, 2013 at 6:19 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Sun, Mar 31, 2013 at 08:22:05PM +0200, Umut Tezduyar wrote: --- src/cgtop/cgtop.c | 108

Re: [systemd-devel] /var/log/journal/

Hi, I am seeing the same behavior since I switched from 197 to 198. I have the default journal.conf and all my logs go under /var/log/journal (My /var is tmpfs) where before they were going under /run/log/journal. I haven't investigated it but maybe the default configuration for Storage= is now

[systemd-devel] [PATCH] cgtop: Add cpu time opt and become stdout sensitive

--- src/cgtop/cgtop.c | 122 ++--- 1 files changed, 88 insertions(+), 34 deletions(-) diff --git a/src/cgtop/cgtop.c b/src/cgtop/cgtop.c index eebebf0..f124826 100644 --- a/src/cgtop/cgtop.c +++ b/src/cgtop/cgtop.c @@ -19,9 +19,11 @@ along with

Re: [systemd-devel] [PATCH] cgtop: Add cpu time opt and become stdout sensitive

:23 PM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Mon, Apr 01, 2013 at 10:01:40AM +0200, Umut Tezduyar wrote: Hi Zbigniew, Thank you very much for reviewing. Please find my comments below. On Mon, Apr 1, 2013 at 6:19 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl

Re: [systemd-devel] [PATCH] cgtop: Add cpu time opt and become stdout sensitive

. On Fri, Apr 5, 2013 at 5:58 PM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Fri, Apr 05, 2013 at 05:44:34PM +0200, Lennart Poettering wrote: On Tue, 02.04.13 18:52, Umut Tezduyar (u...@tezduyar.com) wrote: +if (arg_cpu_type == CPU_PERCENT

[systemd-devel] [PATCH] man: link systemd-static-nodes.service

--- man/systemd-tmpfiles.xml|2 ++ units/systemd-static-nodes.service.in |1 + units/systemd-tmpfiles-clean.service.in |2 +- units/systemd-tmpfiles-clean.timer |2 +- units/systemd-tmpfiles-setup.service.in |2 +- 5 files changed, 6 insertions(+), 3

Re: [systemd-devel] [PATCH] man: link systemd-static-nodes.service

. If that is not the case, then systemd-static-nodes.service still needs to be listed somewhere in man list. On Mon, Apr 22, 2013 at 5:03 PM, Kay Sievers k...@vrfy.org wrote: On Mon, Apr 22, 2013 at 3:16 PM, Umut Tezduyar u...@tezduyar.com wrote: --- man/systemd-tmpfiles.xml|2 ++ units

Re: [systemd-devel] [PATCH] man: link systemd-static-nodes.service

, 2013 at 6:27 PM, Tom Gundersen t...@jklm.no wrote: On Mon, Apr 22, 2013 at 5:13 PM, Umut Tezduyar u...@tezduyar.com wrote: The way I see it is systemd-tmpfiles-setup.service is no different than systemd-static-nodes.service except later is restricted to /dev and runs before udev. Hm

[systemd-devel] systemd-coredump large memory allocation

Hi, systemd-coredump allocates 768 mb heap memory to store the core dump. Is it really the right way? Commit: 41be2ca14d34b67776240bc67facf341b156b974 768 mb is pretty big in 32 bit address space. I have roughly 1.6 gb between beginning of the heap and the first shared library so I have enough

Re: [systemd-devel] systemd-coredump large memory allocation

Hi, Thank you for doing this before me. We do not log anything but call log_oom() if realloc() fails. I was wondering if we should do best effort and write what ever we have read up to the failed realloc(). Maybe even append something like ... due to lack of memory, coredump is not complete. I

Re: [systemd-devel] [PATCH 1/1] RFC: Set the Default OOM Score from configuration file

Hi, Should DefaultOOMScore= and DefaultLimit***= be really under [Manager]? Wouldn't it be better to have an [Exec] section. Or even have [Service], [Mount],.. sections that can give separate configuration per exec unit. Other idea would be having both [Manager] and [Service], [Mount], .. where

Re: [systemd-devel] [PATCH 1/1] RFC: Set the Default OOM Score from configuration file

On Fri, May 3, 2013 at 4:58 PM, Lennart Poettering lenn...@poettering.netwrote: On Sun, 28.04.13 20:37, Umut Tezduyar (u...@tezduyar.com) wrote: Hi, Should DefaultOOMScore= and DefaultLimit***= be really under [Manager]? Wouldn't it be better to have an [Exec] section. Or even have

[systemd-devel] Masking systemd-journal-flush and setting journal storage to persistent

Hi, I have masked the systemd-journal-flush.service and set the Storage=persistent in journald.conf. Then I have removed the /var/log/journal folder. My expectation on next boot was to see the journal files in /var/log/journal but they have stayed in /run/log/journal. According to man journald,

[systemd-devel] Patch to show systemd generators

Hi, Would you be interested in a patch that shows Systemd + Generators or maybe only Generators? Sample is attached. Thanks[image: Inline image 1] image.png___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

Re: [systemd-devel] Masking systemd-journal-flush and setting journal storage to persistent

Hi, No worries. Maybe you want to add systemd-journal-flush.service to man systemd-journald. Maybe altering the help text as following too: To make the data persistent it is sufficient to create /var/log/journal/ where systemd-journald-flush.service will then store the data. On Mon, May 6,

[systemd-devel] [PATCH 1/2] analyze: show generators on plot

--- src/analyze/systemd-analyze.c | 42 src/core/dbus-manager.c |8 ++ src/core/manager.c|2 + src/core/manager.h|2 + 4 files changed, 48 insertions(+), 6 deletions(-) diff --git a/src/analyze/systemd-analyze.c

Re: [systemd-devel] [PATCH 1/2] analyze: show generators on plot

Attached! Had too much time :) Feel free to dismiss it. On Wed, May 8, 2013 at 6:03 PM, Umut Tezduyar u...@tezduyar.com wrote: --- src/analyze/systemd-analyze.c | 42 src/core/dbus-manager.c |8 ++ src/core/manager.c|2

Re: [systemd-devel] [PATCH 1/2] analyze: show generators on plot

Hi, Attached is a screen shot of the new legend area. It is placed on exactly where the previous text based legend was. On Tue, May 14, 2013 at 8:52 AM, Thomas H.P. Andersen pho...@gmail.comwrote: On Wed, May 8, 2013 at 6:03 PM, Umut Tezduyar u...@tezduyar.com wrote: --- src/analyze

Re: [systemd-devel] Patch to show systemd generators

On Tue, May 14, 2013 at 9:14 AM, Thomas H.P. Andersen pho...@gmail.comwrote: On Mon, May 6, 2013 at 4:07 PM, Tom Gundersen t...@jklm.no wrote: On Mon, May 6, 2013 at 2:51 PM, Lennart Poettering lenn...@poettering.net wrote: On Mon, 06.05.13 14:00, Umut Tezduyar (u...@tezduyar.com) wrote

Re: [systemd-devel] [PATCH 1/2] analyze: show generators on plot

Hi, I have updated the patches with Thomas's suggestion. Thanks. On Tue, May 14, 2013 at 8:52 AM, Thomas H.P. Andersen pho...@gmail.comwrote: On Wed, May 8, 2013 at 6:03 PM, Umut Tezduyar u...@tezduyar.com wrote: --- src/analyze/systemd-analyze.c | 42

[systemd-devel] Build option to disable systemd-tmpfiles services

Hi, Our embedded system doesn't utilize systemd-tmpfiles services. We have the option of masking all systemd-tmpfiles related units but I was wondering if project would be open accepting a patch to disable systemd-tmpfiles during build time. Thanks ___

[systemd-devel] [PATCH] build-sys: option to disable tmpfiles

--- Makefile.am | 52 +--- configure.ac | 9 + 2 files changed, 46 insertions(+), 15 deletions(-) diff --git a/Makefile.am b/Makefile.am index e63563f..54c4582 100644 --- a/Makefile.am +++ b/Makefile.am @@ -280,9 +280,13 @@

Re: [systemd-devel] Build option to disable systemd-tmpfiles services

On Sun, Jun 2, 2013 at 8:48 AM, Tom Gundersen t...@jklm.no wrote: On Sun, Jun 2, 2013 at 8:41 AM, Umut Tezduyar u...@tezduyar.com wrote: Attached. Thanks. You don't need to change systemd-update-utmp.service. It is ok to be After= a nonexistent service. Cheers, Tom PS It is easier

[systemd-devel] [PATCH] manager: add DefaultEnvironment option

--- man/systemd-system.conf.xml | 21 + man/systemd.exec.xml| 5 +++-- src/core/load-fragment.c| 8 ++-- src/core/main.c | 5 + src/core/manager.c | 12 src/core/manager.h | 1 + src/core/system.conf|

Re: [systemd-devel] systemd-shutdown static linking (was: Please proof-read: ...)

Hi, Those 2 lines were added on 89b1d5e0e49d3b3501e5f3aadcad712290bcd9bf and the commit log explains why we needed them. / can be treated as special case and excluded. Thanks. On Tue, Jun 11, 2013 at 9:19 AM, Ross Lagerwall rosslagerw...@gmail.comwrote: On Mon, Jun 10, 2013 at 08:30:40PM

[systemd-devel] [PATCH] core: switch to journal when socket is listening

systemd starts using journal as soon as the journal socket is in listening state instead of waiting for journal's socket to switch to 'running' state. --- src/core/manager.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/core/manager.c b/src/core/manager.c index

Re: [systemd-devel] [PATCH] core: switch to journal when socket is listening

On Thu, Jun 13, 2013 at 9:26 PM, Umut Tezduyar u...@tezduyar.com wrote: systemd starts using journal as soon as the journal socket is in listening state instead of waiting for journal's socket to switch to 'running' state. --- src/core/manager.c | 3 ++- 1 file changed, 2 insertions(+), 1

Re: [systemd-devel] [PATCH] core: switch to journal when socket is listening

On Thu, Jun 13, 2013 at 9:26 PM, Umut Tezduyar u...@tezduyar.com wrote: systemd starts using journal as soon as the journal socket is in listening state instead of waiting for journal's socket to switch to 'running' state. --- src/core/manager.c | 3 ++- 1 file changed, 2 insertions

Re: [systemd-devel] [PATCH] manager: add DefaultEnvironment option

On Sun, Jun 9, 2013 at 7:08 AM, Umut Tezduyar u...@tezduyar.com wrote: --- man/systemd-system.conf.xml | 21 + man/systemd.exec.xml| 5 +++-- src/core/load-fragment.c| 8 ++-- src/core/main.c | 5 + src/core/manager.c | 12

Re: [systemd-devel] [PATCH] Describe handling of an AF_UNIX socket

On Fri, Jun 21, 2013 at 10:07 AM, Łukasz Stelmach l.stelm...@samsung.com wrote: It was 2013-06-20 czw 20:57, when Lennart Poettering wrote: On Wed, 19.06.13 14:59, Łukasz Stelmach (l.stelm...@samsung.com) wrote: Describe how to handle an AF_UNIX socket, with Accept set to false, received from

Re: [systemd-devel] [PATCH] core: switch to journal when socket is listening

On Thu, Jun 20, 2013 at 9:15 PM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 19.06.13 13:36, Umut Tezduyar (u...@tezduyar.com) wrote: Hi Lennart, I didn't quite understand how this could end up in a deadlock (http://lists.freedesktop.org/archives/systemd-devel/2013-June/011404

Re: [systemd-devel] test-ipv4ll never finishes

Thanks. I will take a look at it. On Aug 30, 2014, at 3:08 PM, Jan Janssen medhe...@web.de wrote: Hi, on my system, test-ipv4ll waits forever on an epoll: $ strace ./test-ipv4ll execve(./test-ipv4ll, [./test-ipv4ll], [/* 64 vars */]) = 0 brk(0) =

Re: [systemd-devel] Journal Log Persistence without restart of service

> On Apr 25, 2016, at 5:43 AM, Andrei Borzenkov wrote: > > 24.04.2016 19:24, Renjith Vijayan пишет: >> Hi All, >> >> I am trying to make journal logs persistent across reboots in my platform. >> Currently /var/log is mounted on volatile partition in the platform. >> I have

[systemd-devel] [PATCH] sd-dhcp-client: prevent timer related memory leaks

--- src/libsystemd-dhcp/sd-dhcp-client.c |6 ++ 1 file changed, 6 insertions(+) diff --git a/src/libsystemd-dhcp/sd-dhcp-client.c b/src/libsystemd-dhcp/sd-dhcp-client.c index ec2b53f..84d38f0 100644 --- a/src/libsystemd-dhcp/sd-dhcp-client.c +++ b/src/libsystemd-dhcp/sd-dhcp-client.c @@

  1   2   3   4   >