Re: [systemd-devel] timers always run when time changes

The custom time syncing service file does not have "Before=time-sync.target". In fact, not only when the time changes by the custom time syncing service ,but also when I set the time manually by "date -s 2015-05-01 11:08:00", the timer and the same-name service will run. Here is the custom time

Re: [systemd-devel] timers always run when time changes

On Thu, Apr 30, 2015 at 6:35 PM, Likang Wang wrote: > Hi all, > > The entire system is running on an embedded box, and the system time will be > set to 2008-01-01 00:00:00 after every reboot. My app running on the box > will get the real time from my server and update time on the box after every >

[systemd-devel] timers always run when time changes

Hi all, I hava a timer with the fellowing setting: # cat /lib/systemd/system/updateimage.timer [Unit] Description=Update image DefaultDependencies=false [Timer] OnCalendar=*-*-* 02:00:00 Persistent=false [Install] WantedBy=multi-user.target And I want the timer call the same-name service only

Re: [systemd-devel] initrd mount inactive

Lennart Poettering wrote on 04/30/2015 02:39:45 AM: > On Wed, 29.04.15 12:09, aaron_wri...@selinc.com > (aaron_wri...@selinc.com) wrote: > > > I applied those other commits you listed, and I took a look at the lvm2 > > package, which was being compile with "--disable-udev_sync" and " > > --di

[systemd-devel] journal-.gitignore-add-audit_type-from-name

From 785b1367fedb912e91074360c0961209ac5dc9f8 Mon Sep 17 00:00:00 2001 From: Daniel Buch Date: Thu, 30 Apr 2015 21:20:57 +0200 Subject: [PATCH] journal: .gitignore add audit_type-from-name* --- src/journal/.gitignore | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/journal/.gitignore b

Re: [systemd-devel] tmpfiles versus tmpwatch

On Wed, Apr 29, 2015 at 10:28:26PM +1200, Roger Qiu wrote: > Doesn't relatime still update the time if the file is 1 day old > (regardless of modication time), and the current tmpfiles wipes > files that are older by 10 days? Yes, everything should work with relatime, unless you set tmpfiles cleanu

Re: [systemd-devel] [PATCH] tmpfiles: remember errno before it might be overwritten

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel

Re: [systemd-devel] [PATCH] shared/utmp-wtmp: fix copy/paste error

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel

Re: [systemd-devel] [PATCH] tmpfiles: try to handle read-only file systems gracefully

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel

[systemd-devel] [PATCH] tmpfiles: try to handle read-only file systems gracefully

On read-only filesystems trying to create the target will not fail with EEXIST but with EROFS. Handle EROFS by checking if the target already exists, and if empty when truncating. This avoids reporting errors if tmpfiles doesn't actually needs to do anything. --- This is a rework of a patch I wrot

[systemd-devel] [PATCH] tmpfiles: remember errno before it might be overwritten

--- I'm not sure if this is really necessary right now, but that might change in the future. Saving errno before calling another function is always a good idea. Michael src/tmpfiles/tmpfiles.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/tmpfiles/tmpfiles.c b/sr

[systemd-devel] [PATCH] shared/utmp-wtmp: fix copy/paste error

--- src/shared/utmp-wtmp.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/shared/utmp-wtmp.h b/src/shared/utmp-wtmp.h index 6ac2c7b1c768..5d26ba6fb1d0 100644 --- a/src/shared/utmp-wtmp.h +++ b/src/shared/utmp-wtmp.h @@ -65,7 +65,7 @@ static inline int utmp_wall(

Re: [systemd-devel] network interface down in container

On Thu, 2015-04-30 at 11:44 +0200, Lennart Poettering wrote: > On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > > > I used to boot the container this way : > > # systemd-nspawn --network-bridge=br0 -bD /path_to/my_container > > > > Is this correct? > > Looks fine. > >

Re: [systemd-devel] [Q] About supporting nested systemd daemon

On Wed, Feb 25, 2015 at 6:48 PM, Lennart Poettering wrote: > On Wed, 25.02.15 00:05, Cyrill Gorcunov (gorcu...@gmail.com) wrote: > >> Hi all! I would really appreciate if someone enlighten me if there is some >> simple >> solution for the problem we met in OpenVZ: modern containers are mostly >>

Re: [systemd-devel] pam_systemd.so indirectly calling pam_acct_mgmt

On Thu, 2015-04-30 at 15:01 +0200, Lennart Poettering wrote: > On Thu, 30.04.15 08:54, Stephen Gallagher (sgall...@redhat.com) > wrote: > > > Does set-linger persist across reboots? > > Yes it does. When a systemd is booted up with a user that has > lingering on this means that his user@.servic

Re: [systemd-devel] pam_systemd.so indirectly calling pam_acct_mgmt

On Thu, 30.04.15 08:54, Stephen Gallagher (sgall...@redhat.com) wrote: > Does set-linger persist across reboots? Yes it does. When a systemd is booted up with a user that has lingering on this means that his user@.service instance is invoked at boot, without waiting for any login. Lennart --

[systemd-devel] networkd: dbus API for networkd reconfiguration at run-time

Hi Tom, Lennart, I have some questions regarding dbus API and run-time networkd configuration. I would really appreciate your answers/suggestions. First, when upstreaming BridgeFDB support in networkd, I had (in the first place) a patch composed of 2 parts: - One part for clearing ex

Re: [systemd-devel] pam_systemd.so indirectly calling pam_acct_mgmt

On Thu, 2015-04-30 at 11:36 +0200, Lennart Poettering wrote: > On Wed, 29.04.15 22:24, Jakub Hrozek (jakub.hro...@posteo.se) wrote: > > > ...why exactly does systemd-user need to call the account stack > > for? Again, > > I totally understand session, but account? > > Well, if the user service i

Re: [systemd-devel] network interface down in container

On Thu, Apr 30, 2015, 2:22 PM Lennart Poettering wrote: On Thu, 30.04.15 12:48, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > > <97><8F> 2: host0 > >Link File: n/a > > Network File: n/a > > Type: ether > >State: off (unmanaged) > > HW Address: 0e:7f:c3:fb:25:b1 > >

Re: [systemd-devel] network interface down in container

On Thu, 30.04.15 12:48, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > > <97><8F> 2: host0 > >Link File: n/a > > Network File: n/a > > Type: ether > >State: off (unmanaged) > > HW Address: 0e:7f:c3:fb:25:b1 > > MTU: 1500 So, as it appears networkd does consider

Re: [systemd-devel] network interface down in container

On Thu, 30.04.15 12:18, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering > wrote: > > On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > > > >> I used to boot the container this way : > >> # systemd-nspawn --network-br

Re: [systemd-devel] network interface down in container

On Thu, Apr 30, 2015 at 12:48 PM, arnaud gaboury wrote: > On Thu, Apr 30, 2015 at 12:18 PM, arnaud gaboury > wrote: >> On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering >> wrote: >>> On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: >>> I used to boot the container

Re: [systemd-devel] network interface down in container

On Thu, Apr 30, 2015 at 12:18 PM, arnaud gaboury wrote: > On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering > wrote: >> On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: >> >>> I used to boot the container this way : >>> # systemd-nspawn --network-bridge=br0 -bD /path_to

Re: [systemd-devel] network interface down in container

On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering wrote: > On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> I used to boot the container this way : >> # systemd-nspawn --network-bridge=br0 -bD /path_to/my_container >> >> Is this correct? > > Looks fine. > >> >> >>

Re: [systemd-devel] [PATCH] treewide: fix typos

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel maili

[systemd-devel] [PATCH] treewide: fix typos

--- man/systemd.unit.xml| 2 +- src/import/export-tar.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index c2e374a94e..0aa1eeac77 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -1250,7 +1250,7 @@

Re: [systemd-devel] network interface down in container

On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > I used to boot the container this way : > # systemd-nspawn --network-bridge=br0 -bD /path_to/my_container > > Is this correct? Looks fine. > > > * > Now on the container side: > > Nothing con

Re: [systemd-devel] initrd mount inactive

On Wed, 29.04.15 12:09, aaron_wri...@selinc.com (aaron_wri...@selinc.com) wrote: > I applied those other commits you listed, and I took a look at the lvm2 > package, which was being compile with "--disable-udev_sync" and " > --disable-udev_rules". I enabled both of those and recompiled both lvm2

Re: [systemd-devel] pam_systemd.so indirectly calling pam_acct_mgmt

On Wed, 29.04.15 22:24, Jakub Hrozek (jakub.hro...@posteo.se) wrote: > ...why exactly does systemd-user need to call the account stack for? Again, > I totally understand session, but account? Well, if the user service is started without the user being logged in (because "loginctl set-linger" was

Re: [systemd-devel] sd-bus vs gdbus on dbus-daemon

Hi Greg, On Wed, Apr 29, 2015 at 5:49 PM, Greg KH wrote: > On Wed, Apr 29, 2015 at 04:08:50PM +0200, Umut Tezduyar Lindskog wrote: >> Hi, >> >> We [1] have noticed that there could be up to %50 performance gain on >> using sd-bus over gdbus on dbus-daemon. For this reason, we have high >> interes

Re: [systemd-devel] sd-bus vs gdbus on dbus-daemon

Hi Simon, On Wed, Apr 29, 2015 at 5:34 PM, Simon McVittie wrote: > On 29/04/15 15:08, Umut Tezduyar Lindskog wrote: >> We [1] have noticed that there could be up to %50 performance gain on >> using sd-bus over gdbus on dbus-daemon. > ... >> gdbus.c >> - g_dbus_proxy_new_for_bus_sync() >> - 50

Re: [systemd-devel] [PATCH] test-socket-util: Fix tests on machines without ipv6 support

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-d

[systemd-devel] [PATCH] test-socket-util: Fix tests on machines without ipv6 support

The test for socket-util already has some code to only do certain tests on machines with ipv6 support. However this was incomplete causing the test to still fail on such machines, this patch adds the remaining cases required to make it pass on machine without ipv6 support. --- src/test/test-socket

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel mailing list systemd-de

[systemd-devel] network interface down in container

I already used for a while a container (Arch on Arch). I had two distinct IP and a working setup thanks to good help from Tom Gundersen I am trying to replicate my network settings on a new setup (Fedora on Arch). For now, I am just trying with DHCP. Here the setup on host: -