Re: [systemd-devel] Systemd spends much time about 30 seconds for every unit

On Fri, Jun 07, 2019 at 03:48:58AM +, 程 书意 wrote: > Hi all, > > I am working on virtualization on armv8 platform and encountered a complex > problem. From the below boot log, we can find: > > 1. Every unit init need about 30 seconds. > 2. status_printf function doesn't work. [no

Re: [systemd-devel] systemd and chroot()

On Tue, Jun 04, 2019 at 12:42:35PM -0400, Steve Dickson wrote: > Hello, > > We are adding some new functionality to the NFS server that > will make it a bit more container friendly... > > This new functionality needs to do a chroot(2) system call. > This systemcall is failing with EPERM due

Re: [systemd-devel] How to get hardware watchdog status when using systemd

On Tue, May 28, 2019 at 01:50:53PM +0200, Wiktor Kwapisiewicz wrote: > Hi Zbyszek, > > On 28.05.2019 13:43, Zbigniew Jędrzejewski-Szmek wrote: > >What kind of information are you after? > > One interesting statistic I'd like to see changing is the time when > the wa

Re: [systemd-devel] How to get hardware watchdog status when using systemd

On Tue, May 28, 2019 at 12:59:27PM +0200, Wiktor Kwapisiewicz wrote: > Hello, > > I've enabled "RuntimeWatchdogSec=30" in /etc/systemd/system.conf > (after reading excellent "systemd for Administrators" series [0]). > > Before enabling that "wdctl" printed nice statistics but now it only >

Re: [systemd-devel] Node.js sd-notify module visibility

On Thu, May 23, 2019 at 12:43:27PM +0100, Rory Bradford wrote: > Yup, go for it. Done. Zbyszek > On 23/05/2019 12:36, Zbigniew Jędrzejewski-Szmek wrote: > > On Thu, May 23, 2019 at 12:27:56PM +0100, Rory Bradford wrote: > >> Yeah of course, didn't even think. I'm happy wi

Re: [systemd-devel] Node.js sd-notify module visibility

3, 2019 at 12:05 PM Zbigniew Jędrzejewski-Szmek > > mailto:zbys...@in.waw.pl>> wrote: > > > > On Thu, May 23, 2019 at 09:25:02AM +0100, Rory Bradford wrote: > > > Hi, > > > > > > I actively maintain a Node.js module "sd-

Re: [systemd-devel] Node.js sd-notify module visibility

n 23/05/2019 10:04, Zbigniew Jędrzejewski-Szmek wrote: > > On Thu, May 23, 2019 at 09:25:02AM +0100, Rory Bradford wrote: > >> Hi, > >> > >> I actively maintain a Node.js module "sd-notify" available on GitHub > >> (https://github.com/roryr

Re: [systemd-devel] Node.js sd-notify module visibility

On Thu, May 23, 2019 at 09:25:02AM +0100, Rory Bradford wrote: > Hi, > > I actively maintain a Node.js module "sd-notify" available on GitHub > (https://github.com/roryrjb/sd-notify) and npm > (https://www.npmjs.com/package/sd-notify) that has been contributed to > and is being used by others. As

Re: [systemd-devel] Does "systemctl daemon-reload" discard service information?

On Mon, May 20, 2019 at 03:36:28PM +0200, Ulrich Windl wrote: > Hi! > > I have had the effect that a "systectl status" before and after a > "daemon-reload" is different, while the service in question wasn't restarted: Whenever making a report like this, always include the exact systemd version

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

On Thu, May 16, 2019 at 12:04:28PM +0200, Ulrich Windl wrote: > >>> Lennart Poettering schrieb am 16.05.2019 um 10:29 > in > Nachricht <20190516082910.GA24042@gardel-login>: > > On Do, 16.05.19 08:55, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) > wrote: > > > >> Hi! > >> > >> After having

Re: [systemd-devel] systemctl list all possible (including unloaded) services

On Fri, May 10, 2019 at 09:27:17AM -0600, Roger Pack wrote: > Hello, I'm trying to answer this question: > > https://unix.stackexchange.com/questions/517872/systemctl-list-all-possible-including-disabled-services > > Basically, I have a my_service.service that is disabled, I wish I > could "see

Re: [systemd-devel] systemd-coredump[2529]: Process 2326 (xfwm4) of user 1000 dumped core maybe because of lightdm[2482]: gkr-pam: unable to locate daemon control file

On Mon, Apr 29, 2019 at 09:32:57PM +0200, linuxfr...@gmx.at wrote: > Hi Zbyszek, > > > i've already did this. > > It started after desktop freezes here: > > https://forum.manjaro.org/t/xfce-desktop-freezes-after-automated-screen-lock-manjaro-18-0-4-illyria/84717/12 > > which were solved, but

Re: [systemd-devel] systemd-coredump[2529]: Process 2326 (xfwm4) of user 1000 dumped core maybe because of lightdm[2482]: gkr-pam: unable to locate daemon control file

On Mon, Apr 29, 2019 at 09:22:30PM +0200, linuxfr...@gmx.at wrote: > Hi, > > i do not know who is the correct person / mailing list, to ask for this one. > > 1) screen-lock locks the screen  (OK) > > 2) screensaver comes and screen is going to be black.  (OK) > > 3) Everytime i unlock my

Re: [systemd-devel] systemd prerelease 242-rc1

On Wed, Apr 03, 2019 at 07:55:42AM +, systemd tag bot wrote: > A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the > tarball here: Please ignore this one. The version number was not bumped properly. v242-rc2 has already been tagged. Zbyszek

Re: [systemd-devel] WantedBy=default.target

On Thu, Mar 07, 2019 at 11:31:18AM +0100, Michael Biebl wrote: > Am Do., 7. März 2019 um 11:24 Uhr schrieb Lennart Poettering > : > > > > On Do, 07.03.19 10:30, Michael Biebl (mbi...@gmail.com) wrote: > > > > > Looks like quite a few services use > > > WantedBy=default.target > > >

[systemd-devel] planned v241 release

Hi everyone, 241 will be released soon. Current list of outstanding tickets [1]: "23 wireguard peers hang systemd-networkd" #11404 opened 3 days ago by darkk network: wait for kernel to reply ipv6 peer address #11428 (needs review) "Bump numbers for v241" #11387 (release mechanics) "Add

Re: [systemd-devel] Bugfix release(s)

On Tue, Jan 15, 2019 at 01:09:16PM +0100, Lennart Poettering wrote: > On Mo, 14.01.19 11:26, Dave Reisner (d...@falconindy.com) wrote: > > > > > > Well, that sounds as if you want to volunteer as release engineer? ;-) > > > > > > Thing is, we are understaffed. I too have a wishlist of things I'd >

Re: [systemd-devel] Requires and After

On Wed, Jan 02, 2019 at 07:14:10PM +1100, Michael Chapman wrote: > On Wed, 2 Jan 2019, Olaf van der Spek wrote: > > On Wed, Jan 2, 2019 at 4:22 AM James Feeney wrote: > > > systemd has two different classes of "dependencies": 1) "activation" > > > dependencies, and 2) "ordering" dependencies. >

Re: [systemd-devel] Requires and After

On Sun, Dec 30, 2018 at 12:05:46PM +0100, Olaf van der Spek wrote: > Hi, > > Evverx suggested I ask here @ https://github.com/systemd/systemd/issues/11284 > It's about Requires and After. I think a unit in Requires should imply > that unit in After too, otherwise the requirement isn't really met.

[systemd-devel] systemd 240 released

Steve Ramage, Susant Sahani, Sven Joachim, Sylvain Plantefève, Tanu Kaskinen, Tejun Heo, Thiago Macieira, Thomas Blume, Thomas Haller, Thomas H. P. Andersen, Tim Ruffing, TJ, Tobias Jungel, Todd Walton, Tommi Rantala, Tomsod M, Tony

[systemd-devel] systemd hackfest talking points

Hi, we had a systemd hackfest/talkfest last Sunday in Berlin as part of AllSystemdGo 2018. Here is a copy of the doc we used to discuss the technical & documentations topics: https://docs.google.com/document/d/12mWXZem7IOc9u-Db04Cy-NPi39LijiiMlTqX-0DYO98/edit (I tried to convert this to text,

Re: [systemd-devel] [PATCH v2] meson: use the host architecture compiler/linker for src/boot/efi

On Fri, Sep 28, 2018 at 01:19:27PM +0100, Simon McVittie wrote: > On Fri, 28 Sep 2018 at 10:40:28 +0200, Lennart Poettering wrote: > > On Do, 27.09.18 17:17, Helmut Grohne (hel...@subdivi.de) wrote: > > > > > cross building systemd to arm64 presently fails, because the build > > > system uses

Re: [systemd-devel] systemd behavior during shutdown

On Wed, Sep 19, 2018 at 05:01:33AM +, Tiwari, Hari Sahaya wrote: > Hi, > > I am facing one issue with systemd where systems socket is not opening a new > connection during shutdown. > I get below logs, > > Sep 12 20:01:32 jara2 systemd[1]: mytestX.socket: Incoming traffic > Sep 12 20:01:32

Re: [systemd-devel] When is a unit "loaded"?

On Wed, Jul 11, 2018 at 06:52:12PM -0700, Filipe Brandenburger wrote: > Hey Daniel! > > On Wed, Jul 11, 2018 at 5:16 PM Daniel Wang wrote: > > I have a unit, say foo.service, on my system that's in > > /usr/lib/systemd/system, but disabled by preset. > > Not that it matters, but presets don't

[systemd-devel] upcoming systemd-239 release

Hi all, we plan to release systemd-239 wednesday-ish. On Friday we merged the last batch of new features, and until the release, only bug fixes, cleanups, and documentation improvements should be merged. Please test and report any regressions. I'll be making builds for Fedora in copr (*):

Re: [systemd-devel] Running a service *just* before unmounting filesystems

On Wed, Jun 13, 2018 at 04:55:27PM +0200, Hans de Goede wrote: > Hi, > > On 12-06-18 19:11, Lennart Poettering wrote: > >On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote: > >>AFAIK the service actually doing the updates is supposed to call > >>systemctl reboot --force when it is

Re: [systemd-devel] [PATCH] detect-virt: do not return exit failure code when the state is none

On Fri, May 25, 2018 at 10:25:08AM +0200, Franck Bui wrote: > Hi Joey, > > On 05/25/2018 09:33 AM, joeyli wrote: > > > > Do you have good idea to inhibit the exit failure to avoid the subsequent > > activity be blocked? > > > > For the context the actual rule is: > > SUBSYSTEM=="memory",

Re: [systemd-devel] option to wait for pid file to appear

On Thu, May 17, 2018 at 12:12:10PM +0200, Igor Bukanov wrote: > On 17 May 2018 at 11:58, Mantas Mikulėnas wrote: > > Have you tried without the PIDFile= setting at all? > > As far as I can see that breaks live updates that nginx supports where > it starts a new process and

Re: [systemd-devel] GPL and unit/conf files

On Fri, May 11, 2018 at 02:21:30PM +0100, Paul Jakma wrote: > Hi, > > logind.conf has a GPL header, as do things like getty@.service. An LGPL header actually, *library*. All you need to do, is to keep the possibility to modify/destribute that .conf file. > If I needed to make changes to

[systemd-devel] github merge rules update

To systemd repo committers: an investigation in https://github.com/systemd/systemd/issues/8665 done by filbranden showed that github's "rebase & merge" button works better than the "squash & merge" version. The authorship and original timestamps on the commit are not mangled. Hence, let's mostly

Re: [systemd-devel] systemd-tmpfiles duplicate line for path, ignoring

On Wed, May 09, 2018 at 09:01:06PM -0600, Chris Murphy wrote: > Hi, > > I see this in the journal > > May 09 14:36:06 f28h.local systemd-tmpfiles[3273]: > [/etc/tmpfiles.d/suspendfix.conf:7] Duplicate line for path > "/proc/acpi/wakeup", ignoring. > > This file contains: > > w

Re: [systemd-devel] Implementing networkd d-bus interface

On Tue, May 08, 2018 at 01:34:58PM -0500, Thad Phetteplace wrote: > Hi systemd developers, > > I'm wondering what the state of development is on the d-bus interface > for systemd-networkd. Currently the interface appears to be minimal, > but I've also seen comments that a full featured API is

Re: [systemd-devel] [PATCH bluez] hid2hci: Fix udev rules for linux-4.14+

On Mon, May 07, 2018 at 04:06:38PM +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Since commit 1455cf8dbfd0 ("driver core: emit uevents when > device is bound to a driver") the kernel started emitting > "bound" and "unbound" uevents which confuse the hid2hci

Re: [systemd-devel] [ty...@mit.edu: Re: Linux messages full of `random: get_random_u32 called from`]

On Wed, May 02, 2018 at 12:23:33PM -0300, Cristian Rodríguez wrote: > El 02-05-2018 a las 6:25, Lennart Poettering escribió: > >On Di, 01.05.18 18:08, Vito Caputo (vcap...@pengaru.com) wrote: > > >Or maybe this confusion is just another iteration of the stuff > >dicussed here?

Re: [systemd-devel] automount EFI system partition to /efi fails

On Wed, Apr 25, 2018 at 11:10:54AM +0200, Lennart Poettering wrote: > On Mi, 25.04.18 07:48, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > > > [6.291607] f28h.local systemd[715]: Followed symlinks /efi → /efi. > > > [6.291643] f28h.local systemd[715]:

Re: [systemd-devel] automount EFI system partition to /efi fails

On Tue, Apr 24, 2018 at 06:47:24PM -0600, Chris Murphy wrote: > https://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/ > *The ESP used for the current boot is automatically mounted to /efi (or > /boot as fallback),* > > systemd-238-7.fc28.1.x86_64 > > I've commented out the

Re: [systemd-devel] automount EFI system partition to /efi fails

On Wed, Apr 25, 2018 at 07:48:13AM +, Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Apr 24, 2018 at 06:47:24PM -0600, Chris Murphy wrote: > > https://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/ > > *The ESP used for the current boot is automatically

Re: [systemd-devel] About supporting relative values (e.g. 50%) in configuration

On Thu, Mar 08, 2018 at 03:48:54PM +0800, ChenQi wrote: > Hi All, > > I'd like to know if systemd community thinks that adding support for > relative values in configuration is a good idea. > > I found a related patch and discussion in >

Re: [systemd-devel] Create a target unit to start & stop a group of services

On Tue, Mar 06, 2018 at 03:07:30AM +, 林自均 wrote: > Anyone? > > John Lin > > 林自均 於 2018年2月27日 週二 下午6:20寫道： > > > Hi Jérémy, > > > > Thank you, but I read the section "Mapping of unit properties to their > > inverses" in the man page > >

[systemd-devel] [ANNOUNCE] systemd v238

, Sylvain Plantefève, Thomas Blume, Thomas Haller, Vito Caputo, Yu Watanabe, Zbigniew Jędrzejewski-Szmek, Марко М. Костић (Marko M. Kostić) — Warsaw, 2018-03-05 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.

Re: [systemd-devel] systemd-sysusers

On Mon, Feb 05, 2018 at 10:21:17AM -0800, Johannes Ernst wrote: > > > On Feb 4, 2018, at 21:56, Michael Chapman wrote: > > > > On Mon, 5 Feb 2018, Johannes Ernst wrote: > >> It appears systemd-sysusers does not create home directories. On the other > >> hand, it picks

Re: [systemd-devel] hash context not closed.

On Mon, Feb 05, 2018 at 09:17:52AM +0100, Stef Bon wrote: > Same error here: > (gcry_md_open without gcry_md_close) > line 901 in src/resolve/resolved-dns-sec.c > while in the same file at 1227 it's done the good way. Indeed. PR submitted: https://github.com/systemd/systemd/pull/8100. Zbyszek

Re: [systemd-devel] How to handle untagged hexvalues in systemd code?

On Mon, Jan 15, 2018 at 06:44:41PM +0100, Olaf Hering wrote: > I submitted a correct and tested patch via > https://github.com/systemd/systemd/pull/7581, which was using > sscanf("0028f0", "%x",). During discussion I was soft-forced to use > systemd helper functions. These (strtoull based)

Re: [systemd-devel] Required kernel version for pid1 only?

On Tue, Jan 09, 2018 at 08:10:55AM +, 林自均 wrote: > Hi folks, > > I saw the following lines in README: > > > REQUIREMENTS: > > Linux kernel >= 3.13 > > Linux kernel >= 4.2 for unified cgroup hierarchy support > > I guess it means that some part of the whole systemd project

Re: [systemd-devel] Better docs: Word "Type" has two meanings

On Thu, Jan 04, 2018 at 11:54:05AM +0100, Thomas Güttler wrote: >https://www.freedesktop.org/software/systemd/man/systemd.service.html#Type= >> Type: Configures the process start-up type for this service unit. > >https://www.freedesktop.org/software/systemd/man/systemctl.html#-t

Re: [systemd-devel] sdbus-c++, an open source C++ library on top of sd-bus

On Thu, Dec 14, 2017 at 11:09:02AM +, Stanislav Angelovic wrote: > Hi all, > > I would like to let you know that sdbus-c++, our in-house C++ binding for > sd-bus library, has been published open-source at > https://github.com/Kistler-Group/sdbus-cpp in hope that it will be useful. Cool. I

Re: [systemd-devel] [ANNOUNCE] systemd 236

On Fri, Dec 15, 2017 at 06:59:55AM +0300, Andrei Borzenkov wrote: > 15.12.2017 01:17, Lennart Poettering пишет: > > > > * systemctl gained a new --dry-run switch that shows what would be > > done > > instead of doing it, and is currently supported by the shutdown > > and > >

Re: [systemd-devel] moved from systemd 195 to 225, unable to start custom services.

On Fri, Nov 17, 2017 at 05:11:26PM +0530, Shekhar arya wrote: > Hi > > I have upgraded my systemd from older version v195 (used in poky 1.6) to > v225 to resolve some of the memory leak issues. I have resolved all the > dependencies while compilation and now system boots fine. However, after >

Re: [systemd-devel] Why is the [Install] section in a drop-in not respected?

On Tue, Oct 17, 2017 at 09:49:36AM +, 林自均 wrote: > Hi folks, > > I learned that [Install] section in a drop-in is not respected. This > behavior is documented, but I failed to see *why*. > > I found this related GitHub issue: > https://github.com/systemd/systemd/issues/1774, and here is the

Re: [systemd-devel] systemd vs udev automount

On Sun, Oct 08, 2017 at 12:16:33AM -0700, Paul D. DeRocco wrote: > I've got a system (actually two similar systems) built with Yocto that use > systemd, but also have the udev-extraconf package, which includes a udev > rule and associated mount.sh script for automounting. It's doing strange >

Re: [systemd-devel] systemd core dump

On Sun, Oct 08, 2017 at 11:22:00AM +0200, Michael Hirmke wrote: > Hi, > > today systemd crashed on my main server: > > Okt 08 10:06:28 perth systemd[1]: Code should not be reached 'Uh, main > process died at wrong time.' at src/core/service. > c:2701, function service_sigchld_event(). Aborting.

Re: [systemd-devel] A CentOS 7 systemd container in Fedora 27 beta no longer goes beyond /sbin/init, but works on Fedora 26

On Thu, Oct 05, 2017 at 12:23:57PM +, Richard Chan wrote: > Any suggestions on how to instrument systemd inside a CentOS 7 container > (running under docker 1.13 Fedora 27 beta) to determine why it doesn't launch > logind journald dbus-daemon and other units? > > > What is the main reason

Re: [systemd-devel] Hashmap iteration is too costly

On Mon, Jul 17, 2017 at 10:12:12AM +0200, Lennart Poettering wrote: > On Fri, 14.07.17 03:18, vcap...@pengaru.com (vcap...@pengaru.com) wrote: > > > The current hashmap iteration incurs at least one function call per > > iteration, and in my observations using gcc 6.3 w/-g -O2, it's two: > > > >

Re: [systemd-devel] Significant performance loss caused by commit a65f06b: journal: return -ECHILD after a fork

On Tue, Jul 11, 2017 at 09:59:45PM +1000, Michael Chapman wrote: > On Tue, 11 Jul 2017, Lennart Poettering wrote: > >On Tue, 11.07.17 12:55, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote: > > > >>On Tue, 2017-07-11 at 09:35 +0200, Lennart Poettering wrote: > >>>Normally it's dead cheap to check

Re: [systemd-devel] Unknown lvalue 'StartLimitIntervalSec' ?

On Tue, Jul 11, 2017 at 01:55:21AM +0100, Neil MacLeod wrote: > I see that with the following commit, 'StartLimitInterval' is aliased to > 'StartLimitIntervalSec': > > https://github.com/systemd/systemd/commit/f0367da7d1a61ad698a55d17b5c28ddce0dc265a#diff-b3e16bf39e5d7ab233077b9b1dafb095 > >

Re: [systemd-devel] Github systemd issue 6237

On Mon, Jul 10, 2017 at 06:40:00PM +0200, Lennart Poettering wrote: > On Mon, 10.07.17 18:36, Lennart Poettering (lenn...@poettering.net) wrote: > > > > After all (as other people said) systemd has no such requirements > > > itself. It is true that such user names are confusing and > > >

Re: [systemd-devel] Github systemd issue 6237

On Mon, Jul 10, 2017 at 05:03:09PM +0200, Lennart Poettering wrote: > On Mon, 10.07.17 22:23, Michael Chapman (m...@very.puzzling.org) wrote: > > > > Well, it took 3 years or so, until someone noticed the strict rules we > > > enforce. I seriously doubt that naming system users in such unsafe > >

Re: [systemd-devel] Significant performance loss caused by commit a65f06b: journal: return -ECHILD after a fork

On Fri, Jul 07, 2017 at 03:54:09PM -0700, vcap...@pengaru.com wrote: > On Fri, Jul 07, 2017 at 10:34:22PM +0000, Zbigniew Jędrzejewski-Szmek wrote: > > On Fri, Jul 07, 2017 at 02:35:16PM -0700, vcap...@pengaru.com wrote: > > > On Fri, Jul 07, 2017 at 01:49:54PM -0700, vcap...

Re: [systemd-devel] Significant performance loss caused by commit a65f06b: journal: return -ECHILD after a fork

On Fri, Jul 07, 2017 at 02:35:16PM -0700, vcap...@pengaru.com wrote: > On Fri, Jul 07, 2017 at 01:49:54PM -0700, vcap...@pengaru.com wrote: > > On Fri, Jul 07, 2017 at 08:37:08PM +, Mantas Mikulėnas wrote: > > > Back when that commit was made, didn't glibc cache the getpid() result in > > >

Re: [systemd-devel] Github systemd issue 6237

On Wed, Jul 05, 2017 at 08:10:15PM +1000, Michael Chapman wrote: > On Wed, 5 Jul 2017, Colin Guthrie wrote: > >Reindl Harald wrote on 04/07/17 19:50: > >>>When new configuration options are added, the same unit file can > >>>almost always be used with older systemd, and it'll just warn & ignore >

Re: [systemd-devel] Github systemd issue 6237

On Thu, Jul 06, 2017 at 01:43:32AM +0200, Reindl Harald wrote: > > > Am 06.07.2017 um 01:36 schrieb Michael Chapman: > >Note that the semantic validations you're talking about here -- > >things like "does the user exist?" -- are _not_ preemptive. They > >are fatal: the child process will exit

Re: [systemd-devel] Github systemd issue 6237

On Tue, Jul 04, 2017 at 07:36:02PM +0200, Reindl Harald wrote: > > > Am 04.07.2017 um 19:21 schrieb Zbigniew Jędrzejewski-Szmek: > >>My question is: > >> > >>Is this a bug with a BZ against rhel/centos7 (as my understanding is that > >>this affects E

Re: [systemd-devel] Github systemd issue 6237

On Tue, Jul 04, 2017 at 04:59:23PM +, Alexander Bisogiannis wrote: > Hi all, > > https://github.com/systemd/systemd/issues/6237 > > Apologies for asking here, but since the discussion is locked in Github I > thought to ask here. > > This was marked as "not a bug", but in later comments the

Re: [systemd-devel] systemd initrd

On Wed, Jun 28, 2017 at 10:00:53AM -0400, Michael Di Domenico wrote: > can anyone point me towards some howto's or documentation that shows > how one might replace an existing busybox based initrd with a systemd > one? See dracut(8). Zbyszek > > obviously this is a bit of a loaded question as

Re: [systemd-devel] Systemd license vs. libcryptsetup license

On Thu, Jun 08, 2017 at 10:00:03PM +0300, Uoti Urpala wrote: > On Thu, 2017-06-08 at 17:14 +0000, Zbigniew Jędrzejewski-Szmek wrote: > > On Thu, Jun 08, 2017 at 06:03:37PM +0200, Julian Andres Klode wrote: > > > I'm not sure where you get that from. The usual interpretation is

Re: [systemd-devel] Systemd license vs. libcryptsetup license

On Thu, Jun 08, 2017 at 06:03:37PM +0200, Julian Andres Klode wrote: > On Thu, Jun 08, 2017 at 01:47:56PM +0000, Zbigniew Jędrzejewski-Szmek wrote: > > On Thu, Jun 08, 2017 at 09:40:17AM +0200, Krzysztof Jackiewicz wrote: > > > > No, that makes no sense. It'd mean that

Re: [systemd-devel] Systemd license vs. libcryptsetup license

On Thu, Jun 08, 2017 at 09:40:17AM +0200, Krzysztof Jackiewicz wrote: > > No, that makes no sense. It'd mean that putting two zip files that one > > provides > > and the other uses a function with the same name next to one another would > > make them somehow connected and derivatives of one

Re: [systemd-devel] Systemd license vs. libcryptsetup license

On Wed, Jun 07, 2017 at 05:26:21PM +0200, Krzysztof Jackiewicz wrote: > Thanks, for explanation. > > > - a collection of rpms, like a linux distro, including systemd.rpm, > > libcryptsetup.rpm, and thousands of other loosely coupled rpms > > → that's a mere aggregation, each of the thousands

Re: [systemd-devel] Systemd license vs. libcryptsetup license

On Wed, Jun 07, 2017 at 11:47:58AM +0200, Krzysztof Jackiewicz wrote: > > Not sure what "release product under GPL" is supposed to mean. > > The combined work would have to be licensed under GPL according to: > https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility >

Re: [systemd-devel] Systemd license vs. libcryptsetup license

On Tue, Jun 06, 2017 at 04:33:11PM +0200, Krzysztof Jackiewicz wrote: > Hi, > > I noticed that when systemd is configured with libcryptsetup option enabled > it will link to libcryptsetup which is distributed under GPL 2.0. It seems > like a license conflict to me. Can anyone explain it? A

Re: [systemd-devel] renamed link

Please don't top-post. Also try no to spam the mailing list with multiple messages… On Fri, May 19, 2017 at 04:09:08PM +0200, Pascal wrote: > and I'm running/testing on version 232 > > 2017-05-19 16:06 GMT+02:00 Pascal : > > > note that it's about version 210 (year 2014) >

Re: [systemd-devel] renamed link

On Thu, May 18, 2017 at 11:51:25PM +0200, Pascal wrote: > hi, > > I rename my network cards (with udev rule or systemd .link file) in order > to use their new name everywhere else: sysctl, systemd-networkd, samba, > iptables, etc ... > > unfortunately, sysctl and systemd-networkd are started

Re: [systemd-devel] Systemd --session instance?

On Mon, Apr 24, 2017 at 08:09:00PM +, Benno Fünfstück wrote: > Thank you Lennart for taking the time to answer my question. It does make > sense that you wouldn't want to support multiple sessions in big desktop > environments like Gnome or KDE or any complex software. > > However, it seems

Re: [systemd-devel] Systemd --session instance?

On Sun, Apr 23, 2017 at 06:19:16PM +, Benno Fünfstück wrote: > > > > On Sat, Apr 22, 2017 at 02:07:49PM +, Benno Fünfstück wrote: > > > Hello list, > > > > > > currenty, systemd runs a system instance and a per-user one. However, > > > sometimes it would be nice to have a per-session

Re: [systemd-devel] Systemd --session instance?

On Sat, Apr 22, 2017 at 02:07:49PM +, Benno Fünfstück wrote: > Hello list, > > currenty, systemd runs a system instance and a per-user one. However, > sometimes it would be nice to have a per-session instance, for example for > users of lightweight desktop environments that don't have their

[systemd-devel] moving to the meson build system

This is a proposal to move(*) to meson as the build system. Initial, incomplete, implementation is at https://github.com/systemd/systemd/pull/5704. Please have a look, see if it builds on your system, maybe send a patch for some of the missing functionality. Why? I'll just paste the text from

Re: [systemd-devel] nsapwned container terminal background color

On Mon, Mar 20, 2017 at 08:34:02AM +, arnaud gaboury wrote: > > > Are you starting the container manually using systemd-nspawn in a > > terminal > > > emulator window? > > Not really. The container is started at machine boot with > systemd-nspawn@container.service. Then, in one urxvt

Re: [systemd-devel] nsapwned container terminal background color

On Sun, Mar 19, 2017 at 09:30:05PM +, Zbigniew Jędrzejewski-Szmek wrote: > On Sun, Mar 19, 2017 at 04:37:53PM +, arnaud gaboury wrote: > > I am trying with no success to have one background terminal color for the > > host and another one for the container. > &g

Re: [systemd-devel] nsapwned container terminal background color

On Sun, Mar 19, 2017 at 04:37:53PM +, arnaud gaboury wrote: > I am trying with no success to have one background terminal color for the > host and another one for the container. > > Some settings: > - on host: > window manager : i3 > terminal : urxvt-256 > > -on container: > no X, it is a

Re: [systemd-devel] How to set environment variable that is available for later services/shell

On Sat, Mar 11, 2017 at 06:14:17PM +0100, Sam Ravnborg wrote: > Hi all. > > How can we set environment variables so they are available for everyone? > > > Background: > > On an embedded target we use QT applications. > > To start our QT application we need to set environment variables: > >

Re: [systemd-devel] How to unset "uaccess" tag in udev rule?

On Sun, Mar 12, 2017 at 07:38:13PM +0100, Manuel Reimer wrote: > Hello, > > my distributor sets the following rule in /usr/lib/udev/rules.d: > > KERNEL=="uinput", SUBSYSTEM=="misc", OPTIONS+="static_node=uinput", > TAG+="uaccess" > > I think this is not a good idea and that there is a good

Re: [systemd-devel] Question about systemd-firstboot

On Thu, Mar 09, 2017 at 05:31:46PM +0100, Francis Moreau wrote: > On Thu, Mar 9, 2017 at 5:19 PM, Zbigniew Jędrzejewski-Szmek > <zbys...@in.waw.pl> wrote: > > It depends on the command-line parameters: 'ro' and 'rw' both work. > > 'rw' is actually recommended if you're u

Re: [systemd-devel] Question about systemd-firstboot

On Thu, Mar 09, 2017 at 03:49:51PM +0100, Francis Moreau wrote: > On Thu, Mar 9, 2017 at 3:10 PM, Zbigniew Jędrzejewski-Szmek > <zbys...@in.waw.pl> wrote: > > On Thu, Mar 09, 2017 at 10:48:03AM +0100, Francis Moreau wrote: > >> Hello, > >> > >>

Re: [systemd-devel] Question about systemd-firstboot

On Thu, Mar 09, 2017 at 10:48:03AM +0100, Francis Moreau wrote: > Hello, > > I'm puzzled about systemd-firstboot service. > > In my understanding this service is ran only during the firstboot. The > firstboot condition is detected with the presence of /etc/machine-id > file. > > If this file is

Re: [systemd-devel] [ANNOUNCE] systemd 233

On Wed, Mar 01, 2017 at 11:12:03PM +0100, Lennart Poettering wrote: > Heya! > > Finally, here's systemd 233. Tons of new features, even more > bugfixes. Enjoy! > > https://github.com/systemd/systemd/releases/tag/v233 > > CHANGES WITH 233: > > * systemd will now optionally run

Re: [systemd-devel] udev virtio by-path naming

On Wed, Mar 01, 2017 at 06:51:17AM +0300, Andrei Borzenkov wrote: > 01.03.2017 06:43, Zbigniew Jędrzejewski-Szmek пишет: > > > > We could keep an informal list of people who care about specific areas. > > MAINTAINERS file as part of systemd sources? Heh, I really d

Re: [systemd-devel] udev virtio by-path naming

On Tue, Feb 28, 2017 at 08:39:07PM +0100, Lennart Poettering wrote: > On Tue, 28.02.17 19:28, Daniel P. Berrange (berra...@redhat.com) wrote: > > The problem with splitting these rules out into a separate project > > is that there's no other existing place that they would live. The > > "virtio

Re: [systemd-devel] udev virtio by-path naming

On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote: > One could argue about back-level compatibility, but virtio by-path > naming has changed multiple times. We have seen virtio-pci-virtio > (not predictable), pci- and virtio-pci- already. It > might be a good

Re: [systemd-devel] [PATCH] architecture: Add support for the RISC-V architecture.

On Fri, Feb 10, 2017 at 12:45:51PM +, Richard W.M. Jones wrote: > On Fri, Sep 30, 2016 at 04:45:01PM +0100, Richard W.M. Jones wrote: > > Signed-off-by: Richard W.M. Jones > > --- > > src/basic/architecture.c | 14 ++ > > src/basic/architecture.h | 16

Re: [systemd-devel] how to add test sysfs nodes, to sys.tar.xz?

On Mon, Jan 30, 2017 at 05:40:40PM -0500, Dan Streetman wrote: > On Thu, Jan 26, 2017 at 9:36 AM, Zbigniew Jędrzejewski-Szmek > <zbys...@in.waw.pl> wrote: > > Thanks for working on the tests. > > > > On Thu, Jan 26, 2017 at 09:21:41AM -0500, Dan Streetman wrote: >

Re: [systemd-devel] mount ubifs using /dev/ubi0_X path

On Thu, Feb 02, 2017 at 02:11:28PM +0100, Lennart Poettering wrote: > On Mon, 23.01.17 23:02, Mirza Krak (mirza.k...@gmail.com) wrote: > > > 2017-01-23 22:36 GMT+01:00 Mirza Krak : > > > 2017-01-23 18:09 GMT+01:00 Lennart Poettering : > > >> On Mon,

Re: [systemd-devel] New systemd-ui

On Fri, Jan 27, 2017 at 06:34:29PM +0100, Sławomir Lach wrote: > Hi. > > I discovered, there's no recent changes in systemadm/systemd-ui. I > prepared new UI, based on my application logic library, called > libgreattao. Libgreattao generate UI on the fly. The UI is generaated > on the data send

Re: [systemd-devel] how to add test sysfs nodes, to sys.tar.xz?

Thanks for working on the tests. On Thu, Jan 26, 2017 at 09:21:41AM -0500, Dan Streetman wrote: > However, I'd like to also add tests for whitespace replacement using > actual device $attr{}, which I think means the test/sys.tar.xz file > needs to be updated to add device (maybe a NVMe device)

Re: [systemd-devel] What information does machine-id leak?

On Fri, Jan 20, 2017 at 02:02:07PM -0500, Bryan Quigley wrote: > Hi there, > > I see that there is a concern that we need to keep machine-id private > (and local?). I haven't been able to determine exactly why though*. > In most cases it's randomly generated afaict. It's a unique identifier for

Re: [systemd-devel] Skipping temporary coredump file during coredump generation

On Sun, Dec 04, 2016 at 06:24:45AM +, P.R.Dinesh wrote: > Thank you for the insight. > Shall I propose the patch with the following behaviour. > > Check if "backtrace is enabled" or "compression is not enabled or not > supported" > Then store the temporary uncompressed file. > If not skip the

Re: [systemd-devel] Skipping temporary coredump file during coredump generation

On Fri, Dec 02, 2016 at 05:53:59PM +, P.R.Dinesh wrote: > During coredump generation I could find a temporary uncompressed file > getting generated from the corefile and written to the harddisk, later this > file is getting compressed (if compression was enabled) and then the file > coredump

Re: [systemd-devel] Promoting a pull request

On Tue, Nov 22, 2016 at 12:02:41PM +0100, Jouke Witteveen wrote: > On Tue, Nov 22, 2016 at 11:55 AM, Martin Pitt wrote: > > Jouke Witteveen [2016-11-22 11:44 +0100]: > >> I see no way of (trying to) removing the reviewed/needs-rework label > >> in the PR interface. > > > >

Re: [systemd-devel] Promoting a pull request

On Tue, Nov 22, 2016 at 01:07:51PM +0100, Lennart Poettering wrote: > On Tue, 22.11.16 11:44, Jouke Witteveen (j.wittev...@gmail.com) wrote: > > > The contribution guidelines [1] state: > > > > > After you have pushed a new version, try to remove the > > > reviewed/needs-rework label. Also add a

Re: [systemd-devel] journal files interoperability between distros wrt compression

On Wed, Nov 09, 2016 at 02:50:43PM +0100, Michael Biebl wrote: > Hi, > > currently, when trying to opan a Fedora journal file from Debian/Ubuntu I get: > Journal file .../system.journal uses an unsupported feature, ignoring file. > > This is probably due to Debian not having lz4 support enabled

Re: [systemd-devel] getting systemd 232 ready

On Fri, Oct 21, 2016 at 07:12:10PM +0200, Umut Tezduyar Lindskog wrote: > On Fri, Oct 21, 2016 at 7:00 PM, Martin Pitt <martin.p...@ubuntu.com> wrote: > > Hello Zbigniew, Lennart, all, > > > > Zbigniew Jędrzejewski-Szmek [2016-10-20 4:00 +]: > >> Open b

<    1   2   3   4   5   6   7   8   9   10   >