Re: [systemd-devel] [RFC/PATCH] tmpfiles: implement --transform=rpm

On Sun, Mar 2, 2014 at 3:06 AM, Zbigniew Jędrzejewski-Szmek wrote: > + " --transform=rpm Create files list suitable for > RPM %%files section\n" Hmm, can't we maybe come up with something that isn't specific to rpm or dpkg, something that is easily parsed but not bound to

Re: [systemd-devel] Set environment for user@.service

Hi, Before systemd 209, I put 'Environment=ENV=%h/.somedir' in /etc/user@.service.d/env.conf to set some variables. Now since %h is not available for system units anymore, I take the workaround by adding a user unit set-my-env.service: - [Unit] Description=Set systemd environment Befor

[systemd-devel] [RFC/PATCH] tmpfiles: implement --transform=rpm

--- I'm not sure if this can be actually as useful as I envisioned. At least in case of systemd.spec there's a lot of special-casing required, which partially destroys the usefulness of this. Configuration for "normal" packages will hopefully be more straighforward. I made the switch name generic

Re: [systemd-devel] [PATCH] networkd-wait-online: use automatic cleanup

On Sat, Mar 1, 2014 at 10:52 PM, Thomas H.P. Andersen wrote: > From: Thomas Hindoe Paaboel Andersen > > --- > Only compile tested. I just wanted to get rid of the warnings about > use of the uninitialized variables. Applied. Thanks! -t > Makefile.am| 3 ++- > src/netw

[systemd-devel] [PATCH] networkd-wait-online: use automatic cleanup

From: Thomas Hindoe Paaboel Andersen --- Only compile tested. I just wanted to get rid of the warnings about use of the uninitialized variables. Makefile.am| 3 ++- src/network/network-util.h | 28 src/network/networkd-wait-online.c

Re: [systemd-devel] How to build systemd with statically linking

El 01/03/14 15:36, Samuli Suominen escribió: which is a prerequisite for building static lvm2/cryptsetup binaries Just wondering.. why would want to do that ? It is going to break sooner or later.. maybe even worst, it may only appear to work.. Any program remotely useful needs a shared li

Re: [systemd-devel] binding tmpfiles.d to unit startup

On Sat, Mar 1, 2014 at 2:46 PM, Colin Walters wrote: RuntimeDirectory=/run/mydaemon PersistentStateDirectory=/var/lib/mydaemon Btw, see also this thread: https://lists.fedoraproject.org/pipermail/server/2014-February/000843.html Putting these together (and how about we just go ahead and man

Re: [systemd-devel] [PATCH] TODO: Simple conditionals in tmpfiles

On Sat, Mar 01, 2014 at 03:03:17PM +, Colin Walters wrote: > On Fri, Feb 28, 2014 at 9:36 AM, Josh Triplett > wrote: > >--- > > > >Strawman proposal, open to suggestions. > > > ... > > > >+ - Simple conditionals: "C path mode user group - > >(tmpfiles-line)" does tmpfiles-line if path has mod

Re: [systemd-devel] How to build systemd with statically linking

On Sat, 01.03.14 20:36, Samuli Suominen (ssuomi...@gentoo.org) wrote: > > On 01/03/14 20:11, Lennart Poettering wrote: > > On Sat, 01.03.14 17:46, Ȳ�翵 (j-zero.hw...@samsung.com) wrote: > > > >> Hello, > >> > >> I've tried to build systemd(v43) with statically linking. > >> > >> I revised Makefile

Re: [systemd-devel] binding tmpfiles.d to unit startup

On Sat, Mar 1, 2014 at 2:18 PM, Tom Gundersen wrote: And a bit further down that thread there was this proposal from Lennar (which doesn't seem far from what Colin wants): . Right...so rereading that, the discussion seem

Re: [systemd-devel] binding tmpfiles.d to unit startup

2014-03-01 20:18 GMT+01:00 Tom Gundersen : > On Sat, Mar 1, 2014 at 8:04 PM, Michael Biebl wrote: >> 2014-03-01 19:47 GMT+01:00 Colin Walters : >>> On Sat, Mar 1, 2014 at 1:44 PM, Michael Biebl wrote: >>> >>> I vaguely remember that we exactly had this discussion a while ago. >>> >>> >>> Argh, ye

Re: [systemd-devel] binding tmpfiles.d to unit startup

On Sat, Mar 01, 2014 at 02:46:45PM +, Colin Walters wrote: > 2) Loss of association between package data and directory. While > this is >pretty minor, it *is* useful to be able to do rpm -qf /var/kerberos >and see that it comes from the "krb5-libs" package. On a related note, I want to

Re: [systemd-devel] binding tmpfiles.d to unit startup

On Sat, Mar 1, 2014 at 8:04 PM, Michael Biebl wrote: > 2014-03-01 19:47 GMT+01:00 Colin Walters : >> On Sat, Mar 1, 2014 at 1:44 PM, Michael Biebl wrote: >> >> I vaguely remember that we exactly had this discussion a while ago. >> >> >> Argh, yes, possibly. The dangers of getting older... >> >> U

Re: [systemd-devel] binding tmpfiles.d to unit startup

2014-03-01 19:47 GMT+01:00 Colin Walters : > On Sat, Mar 1, 2014 at 1:44 PM, Michael Biebl wrote: > > I vaguely remember that we exactly had this discussion a while ago. > > > Argh, yes, possibly. The dangers of getting older... > > Unfortunately I'm not able to find it in the archives right now.

Re: [systemd-devel] binding tmpfiles.d to unit startup

On Sat, Mar 1, 2014 at 1:44 PM, Michael Biebl wrote: I vaguely remember that we exactly had this discussion a while ago. Argh, yes, possibly. The dangers of getting older... Unfortunately I'm not able to find it in the archives right now. I think if we did talk about it, it was some var

Re: [systemd-devel] binding tmpfiles.d to unit startup

2014-03-01 15:46 GMT+01:00 Colin Walters : > Hi, > > So for OSTree I am trying to move to a model where services populate the > contents of /var on *start*. See previous discussion here: > > https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg07859.html > > The really great part ab

Re: [systemd-devel] How to build systemd with statically linking

On 01/03/14 20:11, Lennart Poettering wrote: > On Sat, 01.03.14 17:46, Ȳ�翵 (j-zero.hw...@samsung.com) wrote: > >> Hello, >> >> I've tried to build systemd(v43) with statically linking. >> >> I revised Makefile.am and spec file but it was not built statically. > We do not support static linking. We

Re: [systemd-devel] How to build systemd with statically linking

On Sat, 01.03.14 17:46, Ȳ�翵 (j-zero.hw...@samsung.com) wrote: > Hello, > > I've tried to build systemd(v43) with statically linking. > > I revised Makefile.am and spec file but it was not built statically. We do not support static linking. We probably should turn this off entirely in the build

Re: [systemd-devel] Creating a Release Tarball

On Sat, 01.03.14 01:36, Justin Brown (justin.br...@fandingo.org) wrote: > Sorry for this very basic question, but I've hit a wall and can't > figure what I need to do. I'm getting started on trying to do some > systemd development. The most natural way for me to compile systemd is > to use the Fed

Re: [systemd-devel] Satitic IP in container

On Sat, Mar 1, 2014 at 3:26 PM, arnaud gaboury wrote: > > >> >> No, --network-bridge=br0 means that a pair of veth devices are created >> (host0 inside the container and vb-* outside), and the vb-* is added >> to your bridge br0. So you should really have host0 in the container >> with this option

Re: [systemd-devel] [PATCH] TODO: Simple conditionals in tmpfiles

On Fri, Feb 28, 2014 at 9:36 AM, Josh Triplett wrote: --- Strawman proposal, open to suggestions. ... + - Simple conditionals: "C path mode user group - (tmpfiles-line)" does tmpfiles-line if path has mode, user, and group: +C /usr/bin/screen 2755 root utmp - d /var/run/screen 0775 ro

[systemd-devel] binding tmpfiles.d to unit startup

Hi, So for OSTree I am trying to move to a model where services populate the contents of /var on *start*. See previous discussion here: https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg07859.html The really great part about this is that one is then able to totally reset O

Re: [systemd-devel] Satitic IP in container

> > No, --network-bridge=br0 means that a pair of veth devices are created > (host0 inside the container and vb-* outside), and the vb-* is added > to your bridge br0. So you should really have host0 in the container > with this option. However, if you don't, which device did this mac > address you

Re: [systemd-devel] Satitic IP in container

On Sat, Mar 1, 2014 at 2:28 PM, arnaud gaboury wrote: >> I suggest simply matching on the name >> instead: "Name=host0". > > I have a problem with this host0. On container, no host0 listed. If I > remember correcty, I shall start systemd-nspawn with some more options, like > --network-veth, right

Re: [systemd-devel] Satitic IP in container

You mean the MAC address of the 'host0' device? This will not be > stable between reboots of the container, so I guess this won't work > (you can verify with "ip link"). You are right, this address changes across reboot. I get rid of this line. I suggest simply matching on the name > instead: "

Re: [systemd-devel] Satitic IP in container

On Sat, Mar 1, 2014 at 9:18 AM, arnaud gaboury wrote: > I set up successful a Arch container managed by systemd-nspsawn. > > I have an issue setting an IP for the container. > > My host is Arch, running custom Kernel 3.13.5-1 (userspace is set) and > systemd-git (lats updated yesterday evening). >

Re: [systemd-devel] How to build systemd with statically linking

El 01/03/14 05:46, 황재영 escribió: Hello, I've tried to build systemd(v43) with statically linking. I revised Makefile.am and spec file but it was not built statically. Do not use static linking, it won't work. also systemd 43 is an ancient relic. ___

Re: [systemd-devel] Creating a Release Tarball

On Sat, Mar 1, 2014 at 8:36 AM, Justin Brown wrote: > commands to prep the repository before creating the tarball. Could > someone enlighten me what steps need to be taken before building the > RPM? $ make distcheck should create a tarball for you. Cheers, Tom _

Re: [systemd-devel] How to build systemd with statically linking

On Sat, Mar 1, 2014 at 12:46 AM, 황재영 wrote: > I've tried to build systemd(v43) with statically linking. That version is ancient. I'm afraid you won't find much help with it here. Have you tried a newer release? ___ systemd-devel mailing list systemd-dev

[systemd-devel] How to build systemd with statically linking

Hello, I've tried to build systemd(v43) with statically linking. I revised Makefile.am and spec file but it was not built statically. systemd: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.25, BuildID[sha1]=0x4afa2d030f0e7d3446aed98

Re: [systemd-devel] Problems with systemd-coredump

On 02/18/2014 11:05 AM, Thomas Bächler wrote: Am 17.02.2014 21:27, schrieb Manuel Reimer: As soon as a bigger coredump (about 500 MB) is to be stored, the whole system slows down significantly. Seems like storing such big amounts of data takes pretty long and is a very CPU hungry process... I

[systemd-devel] Satitic IP in container

I set up successful a Arch container managed by systemd-nspsawn. I have an issue setting an IP for the container. My host is Arch, running custom Kernel 3.13.5-1 (userspace is set) and systemd-git (lats updated yesterday evening). dhcpcd.service is disabled and network is started with these profi