Re: [systemd-devel] systemd log entries
http://www.freedesktop.org/wiki/Software/systemd/catalog/ it is not "in" the journal On Sun, Dec 21, 2014 at 4:21 PM, "Jóhann B. Guðmundsson" wrote: > Why are we spamming the journal with entries like this > > -- Subject: > -- Defined-By: > -- Support: > -- Documentation: > ... > > Dec 21 15:13:25 localhost.localdomain systemd-logind[540]: New seat seat0. > <-- all information required already provided at this point > -- Subject: A new seat seat0 is now available <-- spam > -- Defined-By: systemd <-- more spam > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel <-- > even more more spam > -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat > <-- huge spam > -- > -- A new seat seat0 has been configured and is now available. <-- hello > > JBG > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Watchdog timeout signals
On Mon, Nov 24, 2014 at 5:39 PM, D.S. Ljungmark wrote: > Hi, > We're pondering to use the WatchdogSec=.. function, but wanted to know > what signal (if any) are sent to the application before termination. > > Main reason is that we want to get a proper stacktrace of the daemon if > it is killed for some reason. > You will be glad to hear this (depending on your version): http://cgit.freedesktop.org/systemd/systemd/tree/NEWS#n189 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Unit to test if a domain is reachable
On Thu, Jul 17, 2014 at 11:37 AM, Moviuro wrote: > Hi all! > > Since (from my understanding) systemd devel team did not want to interpret nor > force its interpretation of "network availability" on systemd consumers, we > have to use some other services and cross fingers (network.target, systemd- > networkd-wait-online.service and so on). > Why not just use network-online.target? http://www.freedesktop.org/software/systemd/man/systemd.special.html#network-online.target ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH 1/4] Add ENVIRONMENT to hostnamectl
On Tue, Jul 8, 2014 at 9:31 AM, "Jóhann B. Guðmundsson" wrote: > > On 07/08/2014 12:55 AM, Kay Sievers wrote: >> >> Shouldn't we possibly we find a word for "environment" which explains >> itself a bit better? Environment we usually call the numerous >> variables of a process or service. > > > I was aware of that but decided to move forward since people should be able > to make the distinction vs introduces an new word with added learning curve > but yeah sure I will resubmit with "atmosphere" instead. > How about MachineRole? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system
On Thu, Aug 15, 2013 at 11:04 PM, Reindl Harald wrote: > Please pass 'fsck.mode=force' on the kernel command line rather than creating > /forcefsck on the root file system > > please drop this deprectaion, it is disturbing and useless it is afaik just a step towards read-only / > > if you want a forced fsck for *whatever* reason you do *not* want > to edit the grub-config and need to remove it after pass to prevent > on the next boot a unintented fsck nor do you want to struggle with > the boot-menu on remote-machines > > this warning is pointless and useless > > > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Broken build and CI strategy
On Fri, Jun 28, 2013 at 9:18 AM, Holger Hans Peter Freyther wrote: > On Fri, Jun 28, 2013 at 09:05:40AM +0200, Peter Sztanojev wrote: >> On Fri, Jun 28, 2013 at 8:50 AM, Holger Hans Peter Freyther > >> there already is a jenkins ci for systemd kindly provided by Pantheon: >> http://systemd.getpantheon.com:8080/jenkins/ > > The jenkins script is still using "make test" (which is like calling > "make /tmp"), to execute the tests one would need to call "make check" > but we already had this and it wasn't changed... > So this issue is about tweaking how jenkins does its job? I have added David Strauss to the CC, hopefully he won't mind. >> The output of which can be seen on IRC. >> The problems always seem to come from non-standard/broken setups > > Could you please elaborate on standard vs. non-standard/broken setups. > travis is building on a clean VM and installing most of the packages > specified in the README file. > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Broken build and CI strategy
On Fri, Jun 28, 2013 at 8:50 AM, Holger Hans Peter Freyther wrote: > Dear Lennart, > > the systemd build is currently broken[1] and judging from the commit > history it appears that this happened more than once. Besides fixing > the build you might want to consider adopting another strategy. > > In mature software projects the following is quite common: > > a.) Create a .travis.yml, sync your repo to github[2] and have > travis-ci build your code. My .travis.yml file for systemd is > here[3]. Travis can send email to the repo owners/travis owners > on failed builds. > > b.) Use a combination of gerrit/jenkins. E.g. if you don't want > to have broken builds in master. One would push changes for review to > Gerrit, these would be automatically build on a Jenkins system > and if they compile they can be integrated into the main repository. > The workflow is used in projects like coreboot. > there already is a jenkins ci for systemd kindly provided by Pantheon: http://systemd.getpantheon.com:8080/jenkins/ The output of which can be seen on IRC. The problems always seem to come from non-standard/broken setups > > cheers > holger > > > [1] https://travis-ci.org/zecke/systemde/builds/8530934 > [2] github can create official mirrors of repositories but they only > sync a couple of times/once a day. > [3] https://github.com/zecke/systemde/blob/master/.travis.yml > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] NFS mount unit
On Sat, Feb 16, 2013 at 1:32 PM, Reindl Harald wrote: > > > Am 16.02.2013 13:21, schrieb Peter Sztanojev: >> On Sat, Feb 16, 2013 at 1:12 PM, Reindl Harald >> wrote: >>> >>> >>> Am 16.02.2013 13:05, schrieb Colin Guthrie: >>>> Can't you just make openvpn.service also part of network.target? Thus >>>> holding up network.target until after it's started and thus delaying the >>>> mount until that point (even when the mount is generated from fstab) >>> >>> and would by a lottery openvpn starts sucessful >>> >>> normally you sepcifiy "After=network.target" for OpenVPN >>> because it needs the whole network up to resolve IP >>> of the server and connect >> >> as if network.target means there is network connection up always > > yes, after the target > no, by default network.target only means the network interface is up, it might not even have an IP address > but if you put a service inside network.target which needs the > network connection working at startup how do you make sure > that it always will come up clean you order NetworkManager-wait-online before network.target is one way ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] NFS mount unit
On Sat, Feb 16, 2013 at 1:12 PM, Reindl Harald wrote: > > > Am 16.02.2013 13:05, schrieb Colin Guthrie: >> Can't you just make openvpn.service also part of network.target? Thus >> holding up network.target until after it's started and thus delaying the >> mount until that point (even when the mount is generated from fstab) > > and would by a lottery openvpn starts sucessful > > normally you sepcifiy "After=network.target" for OpenVPN > because it needs the whole network up to resolve IP > of the server and connect > as if network.target means there is network connection up always ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] List configuration dirs in order of a preference
On Fri, Jan 25, 2013 at 11:14 AM, Michal Vyskocil wrote: > It makes an order of a preference more clear without a need to read the > CONFIGURATION FORMAT section. > --- > man/binfmt.d.xml |2 +- > man/modules-load.d.xml |2 +- > man/sysctl.d.xml |2 +- > man/systemd.preset.xml |4 ++-- > man/tmpfiles.d.xml |2 +- > 5 files changed, 6 insertions(+), 6 deletions(-) > > diff --git a/man/binfmt.d.xml b/man/binfmt.d.xml > index 07ae0ac..f27a89a 100644 > --- a/man/binfmt.d.xml > +++ b/man/binfmt.d.xml > @@ -47,8 +47,8 @@ > > > > -/etc/binfmt.d/*.conf > /run/binfmt.d/*.conf > +/etc/binfmt.d/*.conf > /usr/lib/binfmt.d/*.conf > > > diff --git a/man/modules-load.d.xml b/man/modules-load.d.xml > index bcc4d12..263855a 100644 > --- a/man/modules-load.d.xml > +++ b/man/modules-load.d.xml > @@ -46,8 +46,8 @@ > > > > -/etc/modules-load.d/*.conf > /run/modules-load.d/*.conf > +/etc/modules-load.d/*.conf > > /usr/lib/modules-load.d/*.conf > > > diff --git a/man/sysctl.d.xml b/man/sysctl.d.xml > index 69aac8c..438d79f 100644 > --- a/man/sysctl.d.xml > +++ b/man/sysctl.d.xml > @@ -46,8 +46,8 @@ > > > > -/etc/sysctl.d/*.conf > /run/sysctl.d/*.conf > +/etc/sysctl.d/*.conf > /usr/lib/sysctl.d/*.conf > > > diff --git a/man/systemd.preset.xml b/man/systemd.preset.xml > index a692053..53742a8 100644 > --- a/man/systemd.preset.xml > +++ b/man/systemd.preset.xml > @@ -46,11 +46,11 @@ > > > > - > /etc/systemd/system-preset/*.preset > > /run/systemd/system-preset/*.preset > + > /etc/systemd/system-preset/*.preset > > /usr/lib/systemd/system-preset/*.preset > - > /etc/systemd/user-preset/*.preset > > /run/systemd/user-preset/*.preset > + > /etc/systemd/user-preset/*.preset > > /usr/lib/systemd/user-preset/*.preset > > > diff --git a/man/tmpfiles.d.xml b/man/tmpfiles.d.xml > index 785264e..1e9af5e 100644 > --- a/man/tmpfiles.d.xml > +++ b/man/tmpfiles.d.xml > @@ -47,8 +47,8 @@ > > > > -/etc/tmpfiles.d/*.conf > /run/tmpfiles.d/*.conf > +/etc/tmpfiles.d/*.conf > /usr/lib/tmpfiles.d/*.conf > > > -- > 1.7.10.4 > the order is actually what is documented, see for example http://cgit.freedesktop.org/systemd/systemd/tree/src/modules-load/modules-load.c#n201 maybe it's miss-documented somewhere? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] multiseat broken with udl.ko - Fedora 18
please stop spamming the list, we have received the first one On Fri, Jan 18, 2013 at 4:57 PM, poma wrote: > > Bonne journée, > > If brackets can be of any help. > Lennart, have you tested this *new* Fedora's setup, or is this some kind > of zen puzzle? > > Once upon a time, Fedora 17 > # CONFIG_DRM_UDL is not set > CONFIG_FB_UDL=m > multi-seat-x with udlfb.ko(DisplayLink kernel framebuffer driver) worked > like a charm. > > Present time, Fedora 18 > CONFIG_DRM_UDL=m > # CONFIG_FB_UDL is not set > multi-seat-x with udl.ko is broken. > > http://9gag.com/gag/6343044 > > Cheers, > poma > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
