[systemd-devel] [PATCH] fix typo in iDRAC network interface name: irdac-idrac
--- hwdb/20-net-ifname.hwdb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hwdb/20-net-ifname.hwdb b/hwdb/20-net-ifname.hwdb index 29d2633..2408dc1 100644 --- a/hwdb/20-net-ifname.hwdb +++ b/hwdb/20-net-ifname.hwdb @@ -2,4 +2,4 @@ # Dell iDRAC Virtual USB NIC usb:v413CpA102* - ID_NET_NAME_FROM_DATABASE=irdac + ID_NET_NAME_FROM_DATABASE=idrac -- 1.8.5.3 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [ANNOUNCE] systemd 211
On Wed, Mar 12, 2014 at 10:23:26AM +0100, Thomas Bächler wrote:
I had no time to look into this yet, but there's something wrong. I
don't have GPT partitions on this machine (so the generator shouldn't do
anyting), but I get an error during boot:
[4.634733] evey systemd-gpt-auto-generator[226]: Out of memory.
I do have plenty of free memory available, so there is probably an
incorrect log_oom() somewhere in there.
Can you try with attached patch?
--
Tomasz TorczThere exists no separation between gods and men:
xmpp: zdzich...@chrome.pl one blends softly casual into the other.
From ea868942119b7afbfb709253ae6f02d18e67323d Mon Sep 17 00:00:00 2001
From: Tomasz Torcz to...@pipebreaker.pl
Date: Wed, 12 Mar 2014 19:25:11 +0100
Subject: [PATCH] gpt-auto-generator: don't return OOM on parentless devices
---
src/gpt-auto-generator/gpt-auto-generator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gpt-auto-generator/gpt-auto-generator.c
b/src/gpt-auto-generator/gpt-auto-generator.c
index e487f64..19c5eea 100644
--- a/src/gpt-auto-generator/gpt-auto-generator.c
+++ b/src/gpt-auto-generator/gpt-auto-generator.c
@@ -395,7 +395,7 @@ static int enumerate_partitions(dev_t devnum) {
parent = udev_device_get_parent(d);
if (!parent)
-return log_oom();
+return 0;
/* Does it have a devtype? */
devtype = udev_device_get_devtype(parent);
--
1.8.5.3
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] run systemd-tmpfiles-clean only when we have AC power
On Thu, Apr 03, 2014 at 03:42:08PM -0300, Cristian Rodríguez wrote: While it is cool to be neat and clean all the time, this task can wait if we are on battery. What if I connect my laptop to AC only when it sleeps? This will never run. I also don't think couple stats() and rm's have any measurable impact on battery. -- Tomasz TorczOnly gods can safely risk perfection, xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] WTF changed after version 208? systemd won't boot again!
On Mon, Apr 07, 2014 at 06:42:41PM +0800, Aaron Lewis wrote: Hi, I'm sure what changed in version 209, everything is just fine in 208. Now I can't boot my system once again. (Downgrade always works) Here's the problem at boot, I get a dev-sda1.XX timeout message, that's just weird. That's usually a symptom of CONFIG_FHANDLE missing from kernel. -- Tomasz TorczOnly gods can safely risk perfection, xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] mdns support to networkd
On Fri, Jun 20, 2014 at 08:19:17PM +0200, Lennart Poettering wrote: On Sat, 14.06.14 01:13, Vasiliy Tolstov (v.tols...@selfip.ru) wrote: As i see avahi development stopped. Well, yeah, I am doign a shitty job at maintaining it. Does mdns support goes to networkd or no? Well, no. But into systemd-resolved. Our plan is to turn systemd-resolved into an nscd compatible daemon that speaks dns/dnssec, mdns, llmnr, in the long run replacing avahi. Is there a intersection with SSSD? It is quite heavily promoted by one company with color headgear in name, and slighlty conflicts with nscd (and compatibile) solutions: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/usingnscd-sssd.html -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] SIT tunnel does not work
Hi, I've tried to establish SIT tunnel to Hurricane Electric, using systemd v214. It does not work, device do not appear. I'm concerned about networkd discarding part of netlink messages, see below. Original instruction is provided by HE, rest is my shot at translating it into netdev (nb. manpage wasn't updated when tunnel features went in). Original instruction: - modprobe ipv6 ip tunnel add he-ipv6 mode sit remote 216.66.80.162 local 109.107.25.67 ttl 255 ip link set he-ipv6 up ip addr add 2001:470:70:68d::2/64 dev he-ipv6 ip route add ::/0 dev he-ipv6 ip -f inet6 addr $ cat he.netdev --- [NetDev] Name=he Kind=sit [Tunnel] Local=109.107.25.67 Remote=216.66.80.162 $ cat he.network [Match] Name=he [Network] Tunnel=he Address=2001:470:70:68d::2/64 $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd --- timestamp of '/etc/systemd/network' changed he: loaded sit sd-rtnl: discarding 20 bytes of incoming message could not add new link could not add new link eth1: link 3 added eth1: udev initialized link eth1: unmanaged eth1: flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST … -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] SIT tunnel does not work
On Sat, Jun 21, 2014 at 04:36:45PM +0530, Susant Sahani wrote: On 06/21/2014 02:47 PM, Tomasz Torcz wrote: Hi, I've tried to establish SIT tunnel to Hurricane Electric, using systemd v214. It does not work, device do not appear. I'm concerned about networkd discarding part of netlink messages, see below. Original instruction is provided by HE, rest is my shot at translating it into netdev (nb. manpage wasn't updated when tunnel features went in). The se.network file has conf problem. you need to put the interface name rather tunnel name like eth0/em1 Original instruction: - modprobe ipv6 ip tunnel add he-ipv6 mode sit remote 216.66.80.162 local 109.107.25.67 ttl 255 ip tunnel add he-ipv6 mode sit remote 216.66.80.162 local dev eth0 The local IP part comes directly from HE instructionpage. And it works, which is not the case for local dev eth0 version: $ ip tunnel add he-ipv6 mode sit remote 216.66.80.162 local dev eth0 Error: an IP address is expected rather than dev $ rpm -qf /usr/sbin/ip iproute-3.15.0-1.fc21.x86_64 (adding dev works if I ALSO provide local ip part: ip tunnel add he-ipv6 mode sit remote 216.66.80.162 local 109.107.25.67 ttl 255 dev eth0 ) ip link set he-ipv6 up ip addr add 2001:470:70:68d::2/64 dev he-ipv6 ip route add ::/0 dev he-ipv6 ip -f inet6 addr $ cat he.netdev --- [NetDev] Name=he Kind=sit [Tunnel] Local=109.107.25.67 Remote=216.66.80.162 $ cat he.network [Match] Name=he you need to supply the interface name here [Match] Name=em1 ==interface name After putting in interface name tunnel is still not created: # SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd timestamp of '/etc/systemd/network' changed he: loaded sit sd-rtnl: discarding 20 bytes of incoming message could not add new link And no more lines mentioning neither tunnel nor he. -- Tomasz TorczTo co nierealne -- tutaj jest normalne. xmpp: zdzich...@chrome.pl Ziomale na życie mają tu patenty specjalne. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] SIT tunnel does not work
On Thu, Jun 26, 2014 at 11:01:30AM +0530, Susant Sahani wrote: Name=em1 ==interface name After putting in interface name tunnel is still not created: could send do ip link output. Hi, just to recollect, current configuration: he.netdev: -- [NetDev] Name=he Kind=sit [Tunnel] Local=109.107.25.67 Remote=216.66.80.162 he.network: --- [Match] Name=enp5s0 [Network] Tunnel=he Address=2001:470:70:68d::2/64 $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd timestamp of '/etc/systemd/network' changed lan: creating netdev lan: loaded bridge he: loaded sit sd-rtnl: discarding 20 bytes of incoming message veth1: link 41 added veth1: udev initialized link veth1: unmanaged … ip link: 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 4: lan: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UP mode DEFAULT group default link/ether 02:7d:cc:75:ba:e1 brd ff:ff:ff:ff:ff:ff 5: sit0: NOARP mtu 1480 qdisc noop state DOWN mode DEFAULT group default link/sit 0.0.0.0 brd 0.0.0.0 6: virbr1: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default link/ether 52:54:00:78:11:26 brd ff:ff:ff:ff:ff:ff 7: virbr1-nic: BROADCAST,MULTICAST mtu 1500 qdisc pfifo_fast master virbr1 state DOWN mode DEFAULT group default qlen 500 link/ether 52:54:00:78:11:26 brd ff:ff:ff:ff:ff:ff 11: vnet0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master lan state UNKNOWN mode DEFAULT group default qlen 500 link/ether fe:54:00:ea:82:a9 brd ff:ff:ff:ff:ff:ff 12: sixxs: POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP mtu 1280 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500 link/none 17: veth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master lan state UP mode DEFAULT group default qlen 1000 link/ether 6a:d9:7e:0e:20:e2 brd ff:ff:ff:ff:ff:ff 28: vnet1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master lan state UNKNOWN mode DEFAULT group default qlen 500 link/ether fe:54:00:3b:fa:03 brd ff:ff:ff:ff:ff:ff 29: enp4s0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master lan state UP mode DEFAULT group default qlen 1000 link/ether 10:78:d2:8f:6f:59 brd ff:ff:ff:ff:ff:ff 30: enp5s0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 10:78:d2:cc:7e:b0 brd ff:ff:ff:ff:ff:ff alias connected to 88755604DAC8 (eth0) 41: veth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master lan state UP mode DEFAULT group default qlen 1000 link/ether 02:7d:cc:75:ba:e1 brd ff:ff:ff:ff:ff:ff Whereas ”enp5s0” is my external, internet connection. -- Tomasz Torcz ,,If you try to upissue this patchset I shall be seeking xmpp: zdzich...@chrome.pl an IP-routable hand grenade.'' -- Andrew Morton (LKML) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH v2] Use dev_port for the ID of a network device.
On Tue, Jul 01, 2014 at 04:34:14PM +0200, Lennart Poettering wrote: On Tue, 01.07.14 17:26, Samuli Suominen (ssuomi...@gentoo.org) wrote: On 01/07/14 16:20, Kay Sievers wrote: On Tue, Jul 1, 2014 at 3:11 PM, Thadeu Lima de Souza Cascardo casca...@linux.vnet.ibm.com wrote: For network devices on the same PCI function, dev_id should not be used, since its purpose is for IPv6 support on interfaces with the same MAC address. The new dev_port sysfs attribute should be used instead of dev_id. Applied. I'm not complaining, merely verifying, does this mean that udev that will be shipped with systemd-215 will require at least Linux 3.15? Nope. The old logic was broken. The new logic works correctly, but does so only on new kernels. If you run it on old kernels, it will gracefully ignore the id attribute. So, no, it doesn't require the new kernels. It will just start working correctly on new kernels. And on old kernels you will not get the id appended to the name, that's all. Does it mean old (3.15) kernels will see different persistent names with v215? -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ 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 08, 2014 at 08:23:15PM +, Jóhann B. Guðmundsson wrote: On 07/08/2014 07:31 PM, Tollef Fog Heen wrote: ]] Tom Gundersen Patches look good. Only found one tiny nit. We should come up with a better name though, feels wrong that the name is very generic (and clashes with other uses), whilst the usage is quite specific (limited to testing, staging, production). Surely at least qa and dev should go onto that list. (You generally want more than one dev environment too, often one or more per developer.) These days people usually use only 3 tier level ( used to be four back in the day ) as in Development and Integration is done the same tier while Staging and Production are separated tiers altogether. We could extend that and include the fourth tier missing tier ( as in Integration ) as optional for those that prefer 4 tier layer over 3 tier but people moved away form that model to the 3 tier one. Development tier Integration tier Staging tier Production We also have Disaster Recovery (DR) tier. It's basically copy of production, started when disaster strucks. -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. xmpp: zdzich...@chrome.pl Your routes will be aggreggated. -- Alex Yuriev ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] hostnamed: update documentation with new watch chassis type
--- man/hostnamectl.xml | 3 ++- man/machine-info.xml | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/man/hostnamectl.xml b/man/hostnamectl.xml index 7729ef6..eac3040 100644 --- a/man/hostnamectl.xml +++ b/man/hostnamectl.xml @@ -210,7 +210,8 @@ literallaptop/literal, literalserver/literal, literaltablet/literal, -literalhandset/literal, as well as + literalhandset/literal, + literalwatch/literal, as well as the special chassis types literalvm/literal and literalcontainer/literal for diff --git a/man/machine-info.xml b/man/machine-info.xml index 7448e68..244e9b6 100644 --- a/man/machine-info.xml +++ b/man/machine-info.xml @@ -138,7 +138,8 @@ literallaptop/literal, literalserver/literal, literaltablet/literal, -literalhandset/literal, as well as + literalhandset/literal, + literalwatch/literal, as well as the special chassis types literalvm/literal and literalcontainer/literal for -- 1.9.3 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] SIT tunnel does not work
On Sun, Jun 29, 2014 at 01:05:22PM +0200, Tomasz Torcz wrote: he.netdev: -- [NetDev] Name=he Kind=sit [Tunnel] Local=109.107.25.67 Remote=216.66.80.162 he.network: --- [Match] Name=enp5s0 [Network] Tunnel=he Address=2001:470:70:68d::2/64 $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd timestamp of '/etc/systemd/network' changed lan: creating netdev lan: loaded bridge he: loaded sit sd-rtnl: discarding 20 bytes of incoming message Can anyone share examples of _working_ SIT tunnel configuration? -- Tomasz TorczOnly gods can safely risk perfection, xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] SIT tunnel does not work
On Mon, Jul 14, 2014 at 11:18:43AM +0200, Tom Gundersen wrote:
Hi Tomasz,
I just tried with your configuration with current git and it works for
me. Note that your kernel may not yet have received the module
autoloading patch for the tunnel modules (these have been applied to
all currently maintained upstream kernels, but may not have percolated
down to you yet). In that case a manual modprobe sit is necessary
before networkd is started.
Can't get it to work, still. sit modules is loaded:
% lsmod | grep sit
sit26625 0
tunnel413138 1 sit
ip_tunnel 23089 1 sit
When I run SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd,
the two lines mentioning my tunnel are:
he : loaded sit
sd-rtnl: discarding 20 bytes of incoming message
I just tried one way - I've put Tunnel= option into my extarnal
interface configuration:
external.network:
-
[Match]
Name=enp5s0
[Network]
Tunnel=he
DHCP=yes
DNS=192.168.137.3
DNS=127.0.0.1
[DHCPv4]
UseDNS=no
UseHostname=no
-
(previously I had Tunnel= in he.network file).
This resulted in (slightly trimmed):
enp5s0 : DHCPv4 address 109.107.25.67/24 via 109.107.25.1
enp5s0 : setting addresses
sd-rtnl: discarding 20 bytes of incoming message
enp5s0 : added address: fe80::1278:d2ff:fecc:7eb0/64
enp5s0 : added address: 109.107.25.67/24
he : MAC address not found for new device, continuing without
he : link 48 added
he : udev initializing link...
he : netdev has index 48
he : netdev ready
he : flags change: +POINTOPOINT +NOARP
Assertion '({ const typeof(LINK_STATE_ENSLAVING) _y = (LINK_STATE_ENSLAVING);
const typeof(_y) _x = (link-state); unsigned _i; _Bool _found = 0; for (_i =
0; _i 1 + sizeof((const typeof(_x)[]) { LINK_STATE_FAILED, LINK_STATE_LINGER
})/sizeof(const typeof(_x)); _i++) if (((const typeof(_x)[]) { _y,
LINK_STATE_FAILED, LINK_STATE_LINGER })[_i] == _x) { _found = 1; break; }
_found; })' failed at ../src/network/networkd-link.c:1731, function
enslave_handler(). Aborting.
Aborted
systemd-215-2.fc21.x86_64
--
Tomasz TorczOnly gods can safely risk perfection,
xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] SIT tunnel does not work
On Mon, Jul 14, 2014 at 01:05:09PM +0200, Tomasz Torcz wrote: Man, I need coffee. I just tried one way - I've put Tunnel= option into my extarnal I just tried another way - I've put Tunnel= option into my external -- Tomasz TorczOnly gods can safely risk perfection, xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] PGP replacement?
On Sun, Aug 17, 2014 at 08:35:00AM -0400, Mauricio Tavares wrote: So http://blog.cryptographyengineering.com/2014/08/whats-matter-with-pgp.html makes the point that pgp is old school and should be taken to the pasture to die. Like upstart and inetd I take. Is there a replacement built into systemd? If not, I would like to suggest that as something to be integrated into it that would learn from the mistakes of pgp. As PGP stuff has completely nothing to do with basic Linux platform, your post seem to be obvious trolling. Please do not do that. -- Tomasz Torcz ,,(...) today's high-end is tomorrow's embedded processor.'' xmpp: zdzich...@chrome.pl -- Mitchell Blank on LKML ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [ANNOUNCE] systemd 216
On Wed, Aug 20, 2014 at 09:58:09PM +0400, Andrei Borzenkov wrote: В Wed, 20 Aug 2014 13:57:36 +0200 Lennart Poettering lenn...@poettering.net пишет: I do not know how often Android users need to exchange data with Windows via USB stick, but I have to do it pretty often and it sounds like now my timestamps will be wrong. Could you please name commit that does it? The only one I can find close to it (c264aeab4b0e7b69f469e12e78d4a48b3ed7a66e) says actually core: only set the kernel's timezone when the RTC runs in local time which is quite different. No, that's the one. Apparently fat has undocumented (at least in my copy of man page) option time_offset. Of course, GNOME3 does not expect users to be able to configure options for mounting removable devices ... Are you sure about GNOME? https://pipebreaker.pl/dump/gnome-disk-utility-fstab-options.png -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz.. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] basic SO_REUSEPORT support
On Tue, Jul 09, 2013 at 01:01:13PM -0700, Shawn wrote: -- How do you envision using this? Does it even make sense with systemd-managed sockets? -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl-- Baron Vladimir Harkonnen ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fstab Mounts Not Getting Waken Up
On Fri, Jul 12, 2013 at 07:25:04AM -0700, cac...@quantum-sci.com wrote: Lennart Poettering: On Thu, 11.07.13 12:57, cac...@quantum-sci.com (cac...@quantum-sci.com) wrote: I'd understood that if a mount is in fstab, that it should be re-established when the system wakes. But that's not happening. Meaning two sshfs mounts as so: sshfs#carl@droog:/ /media/droogfuse user,auto,_netdev,gid=6,umask=007,cache=no,ServerAliveInterval=15,allow_other,comment=sshfs 0 0 Why would this be? Entries in /etc/fstab that are listed as auto will be mounted at boot, that's all. Not entirely sure what you are referring to as wake? systemd resumes from suspend? I agree, that is how it is -supposed- to work, but as you can see it does not. Yes, when the system wakes from suspend, the drive is never mounted. Resume is not boot. -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. xmpp: zdzich...@chrome.pl Your routes will be aggreggated. -- Alex Yuriev ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] runtime directories for services vs. tmpfiles
On Tue, Jul 16, 2013 at 08:26:23PM +0200, Lennart Poettering wrote: On Tue, 16.07.13 18:53, Lennart Poettering (lenn...@poettering.net) wrote: I can do a mass update to all our packages anyway so the slight change in syntax isn't a problem. Hm, can we take a step back for a moment? It seems that the rpm macros are a fairly complicated solution, and they also don't carry over into debian or arch. User mode sessions also will not work with rpm macros. Well, it's easy to come up with similar macros for debhelper or arch... User session don't really need this, as there as user daemons usually create the dirs they need on their own and there are no privileges involved which might forbid this. I have commite the RPM macro fro now, since either way we will need it for the packages where the dirs need to exist all the time. I discussed this a bit more with Kay on the phone. Here's what we'd propose: I'd be very conservative regarding adding full tmpfiles support into unit files directly. Instead, I'd suggest adding two very minimal, very specific new unit file settings: RuntimeDirectory= RuntimeDirectoyMode= If RuntimeDirectory= is set we'd create it and chown() it to the UID/GID set with User= and Group=. We'd apply the mode specified in RuntimeDirectoryMode= to it. There are daemons which do, in order: 1) start as root 2) open some root-only resources, like network sockets 3) change to less priviledge user 4) if all OK, write PID file or some state in /run 5) do the work Those daemons can't have User= specified, because 2) would fail. And because they must start as root, systemd can't know what chown() to do on runtime dir. So what's the solution? a) declare those daemons incompatible with RuntimeDirectory* stuff - nothing changes, they continue to use separate tmpfile .conf b) fix the daemons? -- Tomasz Torcz God, root, what's the difference? xmpp: zdzich...@chrome.pl God is more forgiving. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] runtime directories for services vs. tmpfiles
On Tue, Jul 16, 2013 at 07:41:08PM +, Jóhann B. Guðmundsson wrote: On 07/16/2013 07:34 PM, Kay Sievers wrote: On Tue, Jul 16, 2013 at 9:28 PM, Jóhann B. Guðmundsson johan...@gmail.com wrote: On 07/16/2013 06:26 PM, Lennart Poettering wrote: I discussed this a bit more with Kay on the phone. Here's what we'd propose: I'd be very conservative regarding adding full tmpfiles support into unit files directly. Instead, I'd suggest adding two very minimal, very specific new unit file settings: RuntimeDirectory= RuntimeDirectoyMode= What exactly are we trying to solve here which should not be fixed upstream in the daemons themselves? Stuff that uses User= cannot be fixed in the daemon itself, at the time it runs, systemd itself has already taken away the privileges to create these directories. We increase unit complexity with each option we add so I would suggest unless it's absolutely necessary to just stick with just tmpfiles to handle this. I second Jóhann. As a packager, I never had problems with separate configuration of runtime dir. Additionally, runtime dirs hardly need customizations by admin. It's not worth exposing them in unit file. -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl-- Baron Vladimir Harkonnen ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] journalctl: add --iso-dates for long timestamps
On Thu, Jul 18, 2013 at 01:36:51AM +0200, Lennart Poettering wrote: On Wed, 17.07.13 17:58, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: +/para/listitem +/varlistentry So, now we have -o short, -o short-monotonic, and --iso-dates. I'm sure we'll add a relative timestamp mode like the excellent one in dmesg --human output in recent util-linux. So I'd say that it makes sense to deprecate short-monotonic and add a new switch --timestamps, --timestamps=monotonic → old short-monotonic --timestamps=iso-date → what you're proposing --timestamps=... This makes the whole thing easier to grok, imo. Journalctl already has 1½ page listing of options... I agree with Zbigniew here. Having this feature sounds useful, but please not in a new switch of its own. However I am not convinced that a --timestamps= switch would be necessary for this either, because I figure that the only --output= mode where iso dates would be useful would be short. It's not useful for the json, json-pretty, json-sse, export, or cat modes, and only semi-useful for verbose mode. It's primarily useful for the short mode. Given that we already have a short-monotonic mode, maybe we should just add more like these? i.e. --output=short-iso or so? If one day we really get multiple modes where ISO dates could be useful then maybe we could internally handles this by considering the --output= param no longer as single value but always as a pair separated by a dash or so. If you follow what I mean. So, yeah, I'd think adding this as --output=short-iso or so would be the nicest? Additional --timestamp would be overkill, I think. New output mode works for me, I will rework the patch. -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] journalctl: add ”short-iso” output format with verbose ISO8601 timestamps
Example:
2013-07-18T10:10:01+0200 sandworm CROND[20957]: (root) CMD (/usr/lib64/sa/sa1 1
1)
---
man/journalctl.xml | 12
src/journal/journalctl.c | 2 +-
src/shared/logs-show.c | 10 +-
src/shared/output-mode.h | 1 +
4 files changed, 23 insertions(+), 2 deletions(-)
diff --git a/man/journalctl.xml b/man/journalctl.xml
index 65a59ea..da43bf2 100644
--- a/man/journalctl.xml
+++ b/man/journalctl.xml
@@ -266,6 +266,18 @@
varlistentry
term
+
optionshort-iso/option
+/term
+listitem
+parais very similar
+but shows ISO 8601
+wallclock timestamps.
+/para
+/listitem
+/varlistentry
+
+varlistentry
+term
optionverbose/option
/term
listitem
diff --git a/src/journal/journalctl.c b/src/journal/journalctl.c
index 9a40d69..9dbe15a 100644
--- a/src/journal/journalctl.c
+++ b/src/journal/journalctl.c
@@ -133,7 +133,7 @@ static int help(void) {
-n --lines[=INTEGER] Number of journal entries to show\n
--no-tail Show all lines, even in follow
mode\n
-r --reverse Show the newest entries first\n
- -o --output=STRING Change journal output mode (short,
short-monotonic,\n
+ -o --output=STRING Change journal output mode (short,
short-monotonic, short-iso\n
verbose, export, json, json-pretty,
json-sse, cat)\n
-x --catalog Add message explanations where
available\n
-l --fullDo not ellipsize fields\n
diff --git a/src/shared/logs-show.c b/src/shared/logs-show.c
index ea47468..353fd2b 100644
--- a/src/shared/logs-show.c
+++ b/src/shared/logs-show.c
@@ -258,6 +258,7 @@ static int output_short(
uint64_t x;
time_t t;
struct tm tm;
+const char *timestamp_format;
r = -ENOENT;
@@ -272,8 +273,13 @@ static int output_short(
return r;
}
+ if (mode == OUTPUT_SHORT_ISO)
+ timestamp_format = %Y-%m-%dT%H:%M:%S%z;
+ else
+ timestamp_format = %b %d %H:%M:%S;
+
t = (time_t) (x / USEC_PER_SEC);
-if (strftime(buf, sizeof(buf), %b %d %H:%M:%S,
localtime_r(t, tm)) = 0) {
+if (strftime(buf, sizeof(buf), timestamp_format,
localtime_r(t, tm)) = 0) {
log_error(Failed to format time.);
return r;
}
@@ -798,6 +804,7 @@ static int (*output_funcs[_OUTPUT_MODE_MAX])(
[OUTPUT_SHORT] = output_short,
[OUTPUT_SHORT_MONOTONIC] = output_short,
+[OUTPUT_SHORT_ISO] = output_short,
[OUTPUT_VERBOSE] = output_verbose,
[OUTPUT_EXPORT] = output_export,
[OUTPUT_JSON] = output_json,
@@ -1076,6 +1083,7 @@ int show_journal_by_unit(
static const char *const output_mode_table[_OUTPUT_MODE_MAX] = {
[OUTPUT_SHORT] = short,
[OUTPUT_SHORT_MONOTONIC] = short-monotonic,
+[OUTPUT_SHORT_ISO] = short-iso,
[OUTPUT_VERBOSE] = verbose,
[OUTPUT_EXPORT] = export,
[OUTPUT_JSON] = json,
diff --git a/src/shared/output-mode.h b/src/shared/output-mode.h
index 0efd430..4012889 100644
--- a/src/shared/output-mode.h
+++ b/src/shared/output-mode.h
@@ -24,6 +24,7 @@
typedef enum OutputMode {
OUTPUT_SHORT,
OUTPUT_SHORT_MONOTONIC,
+OUTPUT_SHORT_ISO,
OUTPUT_VERBOSE,
OUTPUT_EXPORT,
OUTPUT_JSON,
--
1.8.3.1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [IDEA] systemd as basis for HA clusters
On Thu, Jul 25, 2013 at 06:51:21PM +0200, Lennart Poettering wrote: On Fri, 19.07.13 21:05, Pablo Nehab Hess (pa...@hess.net.br) wrote: Hi all, I was wondering how much systemd could add to current high availability cluster setups. Today systemd is used on HA clusters as just an init replacement. However, there are systemd features that might come in handy and improve the overall performance and even reliability of such clusters: * watchdog functionality as in http://0pointer.de/blog/projects/watchdog.html is the most evident feature; * tcp-based dbus communication could be used to exchange information between cluster members; Also, I believe systemd functionality could be extended so it would take into consideration other nodes' systemd instances in order to make sure each service is always alive somewhere -- call it floating units if you will. :-) Does this idea even make sense? Is it too one systemd to rule them all? Well, I don't really know what exactly HA clusters would need. However, note that we actually do try to draw the line somewhere where systemd ends... I have the suspicion the HA cluster stuff something which could make great use of systemd's comprehensive bus interfaces, but I am not convinced such a project should sit in systemd itself. The RH Cluster suite cares about running services, and restarting services when they fail. Just like systemd. Main difference is that you can select on which host to run this service. It could be implemented in some daemon synchronising state between remote systemd's. Every time I use ”clustat” I feel like I'm should be looking at ”systemctl status” listing. When I enable services using ”clusvcadm -e foo” I feel like it should be ”systemctl enable foo”. There's a quite big overlap between cluster suite and systemctl. -- Tomasz TorczFuneral in the morning, IDE hacking xmpp: zdzich...@chrome.plin the afternoon and evening. - Alan Cox ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [Install] question
On Thu, Aug 01, 2013 at 07:48:19AM +0100, lux-integ wrote: Greetings, I am trying to learn to use systemd. I scanned through some of the online manpages and looked at some example unit files. I keep seeing [Install] WantedBy=multi-user.target or [Install] WantedBy=sysinit.target or some such Description of targets is in man systemd.special. I have for example a need to mount stuff (via a mount unit ) then to create directories and copy stuff to them I dont know if these '/bin/mkdir' and '/bin/cp' tasks can be done under '[Install]' They cannot be in mount. There are few way to accomplish what you want, but without details I can provide only vague directions. You need to create unit for your work. You can stuff mkdir into ExecStartPre and cp into ExecStart; you have to make your unit Require the mount unit (or go with the automounter); activation of your work unit should trigger mount. There are few details to work out, like for example usage of PartOf. Ib brief, I dont know what [Install] is for, --what goes under it? --when it is used ? --or not used etc ? --and I cant locate a manpage to explain it. I would be grateful if someone could send me the appropriate URL for 'Install' manpage and or explain what it is and how it is used. Start with man systemd.unit and search for [Install]. All four directives are described there. The information is used by systemctl enable command to create appropriate symlinks. Man pages are also available at http://www.freedesktop.org/software/systemd/man/ -- Tomasz Torcz ,,(...) today's high-end is tomorrow's embedded processor.'' xmpp: zdzich...@chrome.pl -- Mitchell Blank on LKML ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] FYI setroubleshoot has better integration with journald in F20
On Fri, Aug 02, 2013 at 10:14:50AM -0400, Daniel J Walsh wrote: http://danwalsh.livejournal.com/65777.html I think we need a systemctl status -verbose httpd SELinux hints look like perfect fit for existing ”-x” switch. -- Tomasz TorczOnly gods can safely risk perfection, xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Is this the right group for me
On Wed, Nov 20, 2013 at 07:24:18PM +0100, Cecil Westerhof wrote: I have to give a talk about systemd. My colleges are a ‘little’ negative about systemd. So I have some questions about systemd. Someone pointed me to this group, but because of the devel in the name, I was wondering if this would be the right place to post that kind of questions. If you know about a better group … Well, there's always systemd community on G+: https://plus.google.com/communities/114587707547576757881 Generally, if your question isn't answered in manual pages or Lennart's blog post, you can ask here. -- Tomasz Torcz 72-| 80-| xmpp: zdzich...@chrome.pl 72-| 80-| ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-networkd with 802.1x
On Mon, Nov 25, 2013 at 06:20:09PM +1000, David Timothy Strauss wrote: On Mon, Nov 25, 2013 at 5:38 PM, Umut Tezduyar Lindskog umut.tezdu...@axis.com wrote: I would think port access protocols would be needed for servers even before sending a single IP package. I've never used a server that required 802.1x. I've only encountered it in places where physical network access is widespread among people who aren't trusted, like offices and universities. It's utilized with certain high-security environments. Data centers hosting clouds with secure as selling points. It's roughly the same level of paranoia like using SecureBoot on servers, some customers are paying extra for that. -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz.. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Is it possible to start other service units by a service unit which was killed
On Mon, Dec 16, 2013 at 02:26:02AM +0900, Tony Seo wrote: Hello. I send this mail to know whether systemd have options to solve this problem without socket activation. what I have experienced situation is like: If I have A.service, B.service and C.service, I'd like to set [service] in A.service to make others started when A.service is exited(fail, exit .. are not important) Tha would be OnFailure= (described in man systemd.unit). -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. xmpp: zdzich...@chrome.pl Your routes will be aggreggated. -- Alex Yuriev ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Possible net_id incorrect bus and/or slot
On Thu, Jan 09, 2014 at 10:59:34AM +0100, Robert Milasan wrote: Hello, just notice that my network card is named enp0s25, but when I do: # readlink -f /sys/class/net/enp0s25 /sys/devices/pci:00/:00:19.0/net/enp0s25 # lspci |grep Network 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) enp0s25 seems wrong to me, or the slot is based on what? Please clarify how to get this. 0x19 = 25. It's hexadecimal vs decimal. -- Tomasz Torcz ,,(...) today's high-end is tomorrow's embedded processor.'' xmpp: zdzich...@chrome.pl -- Mitchell Blank on LKML ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614
On Wed, Feb 12, 2014 at 08:05:47PM +0100, Reindl Harald wrote: https://bugzilla.redhat.com/show_bug.cgi?id=1047614 Product: Red Hat Enterprise Linux 7 Component:systemd (Show other bugs) Version: 7.0 That's some downstream distro bug. And this is Fedora mailinglist. RHEL issues are offtopic here. -- Tomasz Torcz God, root, what's the difference? xmpp: zdzich...@chrome.pl God is more forgiving. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] https://bugzilla.redhat.com/show_bug.cgi?id=1047614
On Wed, Feb 12, 2014 at 12:45:50PM -0800, David Timothy Strauss wrote: On Wed, Feb 12, 2014 at 12:37 PM, Tomasz Torcz to...@pipebreaker.pl wrote: That's some downstream distro bug. And this is Fedora mailinglist. RHEL issues are offtopic here. This is not a Fedora mailing list at all. Ouch. I'm sorry. I thought I was still reading fedora-devel. My apologies to Harald and other readers of systemd-devel. -- Tomasz Torcz God, root, what's the difference? xmpp: zdzich...@chrome.pl God is more forgiving. pgp8_mNKZFinb.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] core/service: check if mainpid matches only if it set
On Mon, Dec 30, 2013 at 05:26:19PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1047304
-if (s-notify_access == NOTIFY_MAIN pid != s-main_pid) {
+if (s-notify_access == NOTIFY_MAIN s-main_pid != 0 pid !=
s-main_pid) {
I don't think this patch is correct. It only papers over real issue. The
real problem is that systemd sometimes loses state during reload/reexec.
Colin found the problem in [systemd-devel] daemon-reload seems racy.
When the state is lost, services still run, but things happen:
1) main_pid inside systemd is NULL. For Type=notify services this causes:
systemd[1] transmission-daemon.service: Got notification message from PID 1087,
but reception only permitted for PID 0
every time service sends notification to systemd
2) systemctl status service shows the state as DEAD, but the service
still run! Cgroup is not empty, network daemons are still bound to sockets
and continue to serve request.
This state allows admin to issue systemctl start service, but it often
fails immediately - because old process is already bound, and new process
cannot bind to the same port.
systemctl stop service does not work in this case - systemd thinks
service is already dead. To clean up, admin has to systemctl kill service
or kill all service's processes manually, followed by systemctl start.
I'm unable to reproduce this behaviour at the moment
(systemd-208-9.fc20.x86_64),
but I've observed it few times in Fedora 20.
--
Tomasz Torcz ,,(...) today's high-end is tomorrow's embedded processor.''
xmpp: zdzich...@chrome.pl -- Mitchell Blank on LKML
pgpDMxv2wmj6t.pgp
Description: PGP signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [HEADS-UP] It's release time!
On Tue, Feb 18, 2014 at 10:57:23AM +, Jóhann B. Guðmundsson wrote: On 02/18/2014 05:03 AM, Zbigniew Jędrzejewski-Szmek wrote: A related question is wheter Fedora should get this release in rawhide: I think yes, but with --disable-kdbus --enable-compat-libs. It's nice thathttps://bugzilla.redhat.com/show_bug.cgi?id=1065572 got fixed just in time. Rawhide is the place for breakage and we want to catch any related bugs sooner rather then later so why disable kdbus? Because it is not in upstream kernel, therefore not in rawhide. -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz.. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Starting Display Managers
On Tue, Aug 21, 2012 at 11:09:10AM +0600, Alexander E. Patrakov wrote: If the user has a graphics card supported by open-source DRI-based drivers with mandatory KMS, then /dev/dri/card0 (or maybe card1 in dual-gfx setups) is needed. And for Radeon TURKS cards, this only appears after loading firmware (which takes some time). If this is a tablet using the fbdev driver, then /dev/fb0 is needed. And with yet-unsupported graphics cards, the vesa driver only needs /dev/mem or something like that which is always present given a devtmpfs. The question is: how does one write this dependency information, so that lxdm is not attempted to be started before udev creates the necessary device node? Yes, I understand that GPU hotplug in Xorg is the real answer, but we don't have that now, and I don't know how it would cover vesa-based screens. This bug prompted adding CanGraphical property to seat. See http://www.freedesktop.org/wiki/Software/systemd/writing-display-managers lxdm should watch for seat property to change to CanGraphical=yes and then continue initialisation. -- Tomasz Torcz God, root, what's the difference? xmpp: zdzich...@chrome.pl God is more forgiving. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [Feature Request] GET before SET watchdog timeout setting on IPMI compatible hardware
On Tue, Sep 11, 2012 at 11:34:12AM +0530, charles_r...@dell.com wrote: Hello, IPMI watchdog hardware on servers can be configured outside the /dev/watchdog interface[1]. A watchdog timer is provided that implements the Linux-standard watchdog timer interface. What's wrong with ipmi_watchdog module? We should standarise interfaces, not support many similar-yet-different APIs. -- Tomasz Torcz ,,If you try to upissue this patchset I shall be seeking xmpp: zdzich...@chrome.pl an IP-routable hand grenade.'' -- Andrew Morton (LKML) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] Try to start rescue.target if default.target is missing
From 0a3f3b2a46607a94efd2936ae7094a9ef7421e76 Mon Sep 17 00:00:00 2001
From: Tomasz Torcz to...@pipebreaker.pl
Date: Fri, 7 Sep 2012 14:14:44 +0200
Subject: [PATCH] Try to start rescue.target if default.target is missing
In rare cases when default.target symlink is missing, systemd fails
instantly and gets into reboot loop.
Noticed by XReaper on IRC.
Be a bit more resilient, try to fallback to rescue.target first.
---
src/core/main.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/src/core/main.c b/src/core/main.c
index 7b5c861..60e213a 100644
--- a/src/core/main.c
+++ b/src/core/main.c
@@ -1301,7 +1301,17 @@ int main(int argc, char *argv[]) {
r = set_default_unit(SPECIAL_DEFAULT_TARGET);
if (r 0) {
log_error(Failed to set default unit %s: %s,
SPECIAL_DEFAULT_TARGET, strerror(-r));
-goto finish;
+
+ if (arg_running_as == MANAGER_USER)
+ goto finish;
+ else {
+ /* Give administrator a chance to fix things */
+ r = set_default_unit(SPECIAL_RESCUE_TARGET);
+ if (r 0) {
+ log_error(Failed to set %s: %s,
SPECIAL_RESCUE_TARGET, strerror(-r));
+ goto finish;
+ }
+ }
}
/* By default, mount cpu and cpuacct together */
--
1.7.11.4
--
Tomasz Torcz ,,If you try to upissue this patchset I shall be
seeking
xmpp: zdzich...@chrome.pl an IP-routable hand grenade.'' -- Andrew Morton
(LKML)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] Try to start rescue.target if default.target is missing
On Wed, Sep 12, 2012 at 03:17:18PM -0700, Kok, Auke-jan H wrote:
On Wed, Sep 12, 2012 at 3:15 PM, Kok, Auke-jan H
auke-jan.h@intel.com wrote:
On Tue, Sep 11, 2012 at 3:06 AM, Tomasz Torcz to...@pipebreaker.pl wrote:
From 0a3f3b2a46607a94efd2936ae7094a9ef7421e76 Mon Sep 17 00:00:00 2001
From: Tomasz Torcz to...@pipebreaker.pl
Date: Fri, 7 Sep 2012 14:14:44 +0200
Subject: [PATCH] Try to start rescue.target if default.target is missing
In rare cases when default.target symlink is missing, systemd fails
instantly and gets into reboot loop.
Noticed by XReaper on IRC.
Be a bit more resilient, try to fallback to rescue.target first.
+
+ if (arg_running_as == MANAGER_USER)
+ goto finish;
+ else {
ignore that, I just reread your patch and that's what you're actually
doing here, it seems, for the user session, or does it error out for
the user session here?
I had not worked yet with user sessions, the patch was for systemd running as
PID1. default.target may go missing for couple of reasons - disk corruption,
overzealous admin, honest mistake.
Yet Lennart pointed that systemd should cope with that situation, I had to
ask XReaper why in his situation it didn't.
--
Tomasz Torcz ,,If you try to upissue this patchset I shall be
seeking
xmpp: zdzich...@chrome.pl an IP-routable hand grenade.'' -- Andrew Morton
(LKML)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Have timers fire after boot is complete
On Thu, Sep 27, 2012 at 01:43:34PM +0100, Christian Seiler wrote: The problem here is that a Type=idle service is basically a type=simple service and you might want to have Type=forking or Type=oneshot services which you want to start. Maybe sometimes like: [Service] Type=idle RemainAfterExit=yes ExecStart=/usr/bin/systemctl start iamlate.target And create this simple iamlate.target and have your after everything services and scripts have WantedBy=iamlate.target? -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] One of my fundamental problems with systemd...
On Sat, Oct 27, 2012 at 11:59:21AM -0400, Michael H. Warfield wrote: On Sat, 2012-10-27 at 10:05 +0200, Miklos Vajna wrote: On Fri, Oct 26, 2012 at 06:39:33PM -0400, Michael H. Warfield m...@wittsend.com wrote: [root@alcove mhw]# systemctl status network.service network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: failed (Result: exit-code) since Wed, 24 Oct 2012 18:23:07 +0400; 1min 57s ago Process: 91 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=209/STDOUT) CGroup: name=systemd:/system/lxc/Alcove/system/network.service Tells me nothing. Does not tell me where the problem is... What systemd version are you running? Seems some older one, which lacks journal integration, providing the stderr/stdout of the failed service. I guess that would help a lot in your situation. I think you're onto something there. I'm running the latest for Fedora 17 but that's only systemd-44-20. Building that reveals a whole lot of cherry picked patches from git commits. Rawhide has systemd-194-1 and I've now built that for F17 and appears to be a cleaner build. I'm going to test with that one first before moving on to git. Fedora 18 have probably more recent version than rawhide. At last receiving more attention. -- Tomasz TorczTo co nierealne -- tutaj jest normalne. xmpp: zdzich...@chrome.pl Ziomale na życie mają tu patenty specjalne. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Verbose output option when starting daemons manually
On Fri, Nov 09, 2012 at 12:45:22AM +, Jóhann B. Guðmundsson wrote: What's lacking is the status to be shown when units are manually started/reloaded/restart/stopped there is just one slight problem implementing that which is you dont want that output when the service is started at boot time or shutdown... perhaps that could be solved by introducing specific boot-start and shutdown-stop switches which would only be used to start unit or shut down units at boot-up/shutdown We already have verbose indicator, used on boot-up/shutdown; it is responsible for pretty display of Starting foo... [ OK ] Started foo. So this would be if (istty() !show_status) do the journal output -- Tomasz Torcz 72-| 80-| xmpp: zdzich...@chrome.pl 72-| 80-| ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [ANNOUNCE] systemd v196
On Fri, Nov 23, 2012 at 10:29:53AM +0100, Henrik Grindal Bakken wrote: Any ideas? I'm running 196 just fine on a 3.0 vendor kernel, so it's not a universal problem. I also use getty on the serial port, with no local modifications. I believe the requirement for a 3.4 (or something) kernel came in 188 for some logging bits, although I'm not sure. systemd should work just fine without it, though. v189 NEWS: * Support for reading kernel messages from /proc/kmsg has now been removed. If you want kernel messages in the journal make sure to run a recent kernel (= 3.5) that supports reading structured messages from /dev/kmsg (see above). -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Network.service for wifi
On Wed, Dec 05, 2012 at 04:36:04PM -0800, John Tobias wrote: Follow up to my previous message: The systemd need to determine if my firmware of my wifi has been loaded by the kernel. Any idea? Probably device like sys-subsystem-net-devices-wlan0.device will appear. You can use it as an ordering point. -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [RFC] iscsid / systemd / dracut integration effort
On Tue, Dec 11, 2012 at 03:26:46PM -0800, Chris Leech wrote: Thanks, this got me going in the right direction. These unit files seems to be working much better for me, with the startup and shutdown ordering between iscsi, iscsid, and remote-fs mounts sorted out. I'm not sure about the tgtd/targetcli stuff, not sure what the original need there was. After tgtd was added in Fedora for cases when system accesses targets exported by the same system. So targets would be configured first, and only then accessed by iscsid. after tgtd was added, after targetcli is natural expansion of it. -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl-- Baron Vladimir Harkonnen ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] add sprezzos as alias for debian in autoconf script
On Sat, Dec 29, 2012 at 03:30:08PM -0500, nick black wrote: - at some point, either debian or the derivative might lurch in a new direction. in either case, carefully-crafted, minimal new TARGET_-specific code (or however you choose to do it) can mirror the divergence. all scripts continue to work. At this point derevative should stop and think. Is this diversion really needed (hint: almost never is)? What advantages this diversion brings, if any? If it's a good idea, why upstream did not go this way? Systemd project is trying to _get rid_ of distro difference in such trivial matters as hostname file location. Configure options are needed to make adoption easier, but the holy grail would be removing those options. -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz.. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] CoreOS Goal Question: Should we be aiming to be able to boot with an empty /etc?
On Mon, Jan 07, 2013 at 02:54:49PM +0100, Peeters Simon wrote: - Some files are needed quiet hard (passwd, group, shadow ,...) That's not really true, as any consumer of those files should go through getpwname() and similar functions. And glibc implementation of those functions could be made to check some distro-default accounts in /usr/share ... Something like this is done by tcb (http://www.openwall.com/tcb/). tcb is quite cool, by the way, it replaces /etc/shadow with bunch of files accessible by respective users. -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl-- Baron Vladimir Harkonnen ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] CoreOS Goal Question: Should we be aiming to be able to boot with an empty /etc?
On Mon, Jan 07, 2013 at 07:35:54PM +0100, Lennart Poettering wrote: But dynamically allocating system users per-boot and ensuring that /etc and /var matches would still be interesting. Uh, yeah, there's still the question out there what to do with fully dynamic throw-away UIDs, for example so that gdm could allocate a UID for each seat when showing login prompts dynamically. This is going to be really hard, since after dropping a UID again one needs a good way to drop all files and other objects the user created before handing out the same UID again, and I do not see how we could deal with that properly. It smells similar to what Android is doing - separate UID per app. -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl-- Baron Vladimir Harkonnen ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Systemd and network devices under LXC?
On Thu, Jan 24, 2013 at 12:29:41AM -0500, Lars Kellogg-Stedman wrote: BindsTo=sys-subsystem-net-devices-eth0.device Systemd (197) does not appear to be aware of this interface, and ultimately gives up with the following error: Timed out waiting for device sys-subsystem-net-devices-eth0.device. This is what udevadm says about the interface: # udevadm info /sys/class/net/eth0 P: /devices/virtual/net/eth0 E: DEVPATH=/devices/virtual/net/eth0 E: IFINDEX=35 E: INTERFACE=eth0 E: SUBSYSTEM=net What's missing is TAG=systemd, this will make .device in systemd. This tag should be applied by 99-systemd.rules in udev rules directory. -- Tomasz Torcz God, root, what's the difference? xmpp: zdzich...@chrome.pl God is more forgiving. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Someone working on gui for multiseat?
On Mon, Feb 11, 2013 at 09:16:08PM +0100, Lennart Poettering wrote: a) we need to treat all devices of the same type the same, a logic depending on the order of discovery is not possible. Can we treat devices depending on which USB port they are connected to? If so, there could be (custom) udev rule stripping SEAT_MASTER tag from the device connected to specific USB port, solving Stef's issue. -- Tomasz TorczOnly gods can safely risk perfection, xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] RFC: Predictable Network Interface Names
On Wed, Feb 13, 2013 at 07:29:10PM +0100, Kay Sievers wrote: On Wed, Feb 13, 2013 at 7:19 PM, Tomasz Torcz to...@pipebreaker.pl wrote: On Tue, Feb 12, 2013 at 09:07:00AM +0100, Jan Engelhardt wrote: On Monday 2013-01-07 23:29, Lennart Poettering wrote: For your example the new code would pick a name of enp0s0d0, i.e. for pci bus 0, slot 0, and dev_id 0. Is it Solaris time yet? enp0s0d0, that's just like c0t0d0s0. And Heh, just in time when Solaris 11 deprecated such names, choosing to name interfaces as net0, net1, net2 The Solaris disk names are based on meaningless unpredictable enumerations, they have never been topology based. They are just 3 levels deep, which made them only slightly better than a single number, it's still the same useless enumeration with inventing artificial numbers. I don't remember seeing topology based names for network interfaces on Solaris, they did that? Not really, just driver namedetection order - ixgb0, nge1 etc. -- Tomasz TorczFuneral in the morning, IDE hacking xmpp: zdzich...@chrome.plin the afternoon and evening. - Alan Cox ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] howto system-d non-graphical screen
On Wed, Feb 20, 2013 at 09:59:30AM +, lux-integ wrote: On Wednesday 20 February 2013 01:21:37 Kok, Auke-jan H wrote: On Tue, Feb 19, 2013 at 4:58 PM, lux-integ lux-in...@btconnect.com wrote: greetings, I am interested in learning to use systemd with output to an alphanumeric character screen (i.e. non graphical ). Is this doable without delving into shell programming? Examples, guidance, hints, advice etc would be much appreciated. I'm no expert on non-graphical output, but systemd itself is a console/terminal application. There also is no shell code involved in any parts of systemd. Here is in excerpt:- [ if they are shown at all, given we use graphical boot splash technology like Plymouth these days. Nonetheless the information of the boot screens was and still is very relevant, because it shows you for each service that is being started as part of bootup, wether it managed to start up successfully or failed (with those green or red [ OK ] or [ FAILED ] indicators). ] from this link http://0pointer.de/blog/projects/systemd-for-admins-1.html I have looked at the documents on the systemd wikii. The main page has a proud representation of a console boot-screen showing the [ OK ]'s etc. And as I said, I am interested NOT in using 'Plymouth/OR-other-graphical boot- splash-screen but a 'console-boot-screen' with the [ OK ]'s and [ FAILED ]'s etc. Is there documentation available how this is done in systemd? It's not done in systemd. The details are dependent on your distribution; for example you can disable Plymouth graphical screen by removing rhgb from kernel command line in bootloader menu. Text boot is the default, graphical parts are added by distributions. -- Tomasz TorczTo co nierealne -- tutaj jest normalne. xmpp: zdzich...@chrome.pl Ziomale na życie mają tu patenty specjalne. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] OnCalendar= timers crashing systemd
Hi, Carlos Silva, known as r3pek on IRC, found out that some parts of DBUS code weren't updated when introducing calendar events. Specifically, this simple unit: --- crash.timer --- [Unit] Description=update DNS hourly [Timer] OnCalendar=hourly --- is enough to kill systemd by systemctl status crash.timer. The error is: systemd[1]: Assertion 'endswith(t, Sec)' failed at src/core/dbus-timer.c:78, function bus_timer_append_timers(). Aborting. -- Tomasz TorczOnly gods can safely risk perfection, xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Binary launched in ExecStartPre gets killed...
On Mon, Mar 04, 2013 at 07:01:01PM +0100, Lennart Poettering wrote: On Mon, 04.03.13 15:25, Belal, Awais (awais_be...@mentor.com) wrote: Hi, So how do i write such a service i.e. when A starts B should be started first and when A is stopped B should be stopped as well. I am really new to this so any pointers here would be really helpful. I understand that this is a very basic question but I am very new to this... In this case write two normal .service files for these services. Then, to link them together Add BindTo= to their [Unit] sections, pointing to the other unit. This would then make sure, that if one is started, the other is too, and if one is stopped the other is too, and both would be equivalent (are they really? usually they aren't, but you description above suggests two services where one cannot exist without the other, and vice versa...). In addition to that add After=B.service to A.service. (or, alternatively, Before=A.service to B.service, which would be equivalent.) Please note that ordering deps are orthogonal to requirement deps. That means that BindTo= does not imply ordering, and hence you need both 'BindTo=' and 'After=' (or 'Before=') in the [Unit] sections... Lennart, I think we need a blog entry with clear description how to handle situations when service consist of multiple units. Some clear recommendation when to use BindTo=, PartOf=, targets and such. Pretty please :) -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. xmpp: zdzich...@chrome.pl Your routes will be aggreggated. -- Alex Yuriev ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [ANNOUNCE] systemd 198
On Fri, Mar 08, 2013 at 10:26:38AM +0100, Holger Winkelmann wrote: HI, * Resource limits (as exposed by the various control group controllers) can now be controlled dynamically at runtime for all units. More specifically, you can now use a command like systemctl set-cgroup-attr foobar.service cpu.shares 2000 to alter the CPU shares a specific service gets. These settings are stored persistently on disk, and thus allow the administrator to easily adjust the resource usage of services with a few simple commands. This dynamic resource management logic is also available to other programs via the bus. Almost any kernel cgroup attribute and controller is supported. Can you explain how the settings for a particular units are persistently stored. Does systemd write back such values into the particular unit, or are they stored somewhere else? The reason why I'm asking is the facts that stuff like this strives the configuration management functions of a Linux system. These settings are stored persistently on disk goes to. If yo have such setting somewhere else as back in the unit, how do you know those settings exists. If they go back into the unit you obviously overwrite the bootstrap default setting in the unit... may it goes into the sytemd/unite.service.d/ ? Feedback would be welcome ;-) Runtime changes go into /run/systemd/system/unit_id.d/50-unit_name.conf; persistent into /etc/systemd/system/unit_id.d/50-unit_name.conf. I'm no sure what's the difference between ID and name is, I'm just looking at unit_write_drop_in() function. -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. xmpp: zdzich...@chrome.pl Your routes will be aggreggated. -- Alex Yuriev ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] condition: add option ConditionArchitecture
On Tue, Mar 26, 2013 at 04:07:47PM -0300, Cristian Rodríguez wrote: El 26/03/13 15:17, Bill Nottingham escribió: Lukas Nykryn (lnyk...@redhat.com) said: --- TODO | 2 -- man/systemd.unit.xml.in | 8 src/core/condition.c | 16 src/core/condition.h | 1 + src/core/load-fragment-gperf.gperf.m4 | 1 + 5 files changed, 26 insertions(+), 2 deletions(-) Not that this seems wrong, but what is the usage case for this that can't be solved via package (de)installation? The patch looks fine to me, what it solves ? well.. there may be generic image deployments , who contain the same packages but one of them is only really useful in arch s390 or ppc.. etc.. The reason explained on IRC was to automatically start sshd in installer on s390. Currently it is started based on sshd in kernel commandline, but on s390 it must be started always. -- Tomasz TorczOnly gods can safely risk perfection, xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] [RFCv4] Add Listen* to dbus properties
On Tue, Apr 02, 2013 at 05:54:32AM +0200, Zbigniew Jędrzejewski-Szmek wrote: On Mon, Apr 01, 2013 at 11:09:45PM +0300, Oleksii Shevchuk wrote: sockets.socket - Test Loaded: loaded (/home/alxchk/.config/systemd/user/sockets.socket; static) Active: inactive (dead) Listen: Stream: /tmp/stream1 Stream: @stream4 Pushed, but format changed to: listen1.socket - descr descr Loaded: loaded (/run/systemd/system/listen1.socket; static) Active: failed (Result: resources) ListenStream: /tmp/stream1 ListenDatagram: /tmp/stream2 I must say I liked per-type grouping better. -- Tomasz Torcz God, root, what's the difference? xmpp: zdzich...@chrome.pl God is more forgiving. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] TODO: passwd.d, group.d
On Mon, Apr 22, 2013 at 02:53:50PM -0700, Josh Triplett wrote: +* Support passwd.d and group.d; accumulate a persistent name/number map, to + preserve UID/GID assignments without requiring assignment of unique IDs at + adduser time. Hmm, how is that related to systemd code? Sounds more like a glibc shipped feature/plugin? It would involve a PAM plugin as well, yes, but also a system daemon watching those directories for changes and allocating new systemwide UIDs and GIDs, and I also suspect several bits of systemd functionality would want to integrate with it, notably logind and container bits. Don't you want tcb, then? http://docs.altlinux.org/manpages/tcb.5.html -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] wake from sleep on systemd timer
On Tue, May 07, 2013 at 12:10:26AM +0200, Kai Krakow wrote: [...] Meanwhile, where's a good place to contribute my systemd unit files I created for different services that not yet seem to be covered by the systemd distribution? They could also need some review maybe... Upstream - submit the patches to developers of such services. -- Tomasz TorczOnly gods can safely risk perfection, xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH 2/6] readahead-common:fs_on_ssd() stat might not get the real device name
On Fri, Sep 24, 2010 at 12:22:34PM +0200, Kay Sievers wrote: On Fri, Sep 24, 2010 at 12:06, har...@redhat.com wrote: From: Harald Hoyer har...@redhat.com btrfs returns a major(0) for its device, so try to find the mountpoint and real device. + fp = fopen(/proc/self/mountinfo, r); + if (fp == NULL) + return NULL; + while (fscanf(fp, %*s %*s %i:%i %*s %1024s %*s %*s %*s %1024s %*[^\n], maj, min, mp, dev) Using device names from this file is not nice. I have just /dev/root here. Shouldn't we just read the kernel commandline instead? Kernel commandline could have root=UUID or LABEL there... and btrfs is strange beast, being a multi-device filesystem. I believe it could return any of underlaying device and run in raid0, 1, 10, soon raid 5/6 configuration. grubby packages in fedora had similar problem with finding proper root device, see: https://bugzilla.redhat.com/show_bug.cgi?id=530108 for comments and patches. -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fsck and -l switch
On Thu, Nov 25, 2010 at 09:44:41PM +0100, Andrej Gelenberg wrote: Hi, -l break fsch*.service for me. fsck.ext4 don't like it. Besides why -l? From man e2fsck: -l filename Add the block numbers listed in the file specified by filename to the list of bad blocks. The format of this file is the same as the one generated by the badblocks(8) program. You are looking at the wrong man page. Check this commit: http://git.kernel.org/?p=utils/util-linux-ng/util-linux-ng.git;a=commit;h=dd0bd943f94392d165c5903e271c966afb0d7b75 for proper one. In short, -l allow systemd to start fsck for every filesystem on device in the same time and prevents them stepping on each other's toes. -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl-- Baron Vladimir Harkonnen ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] preparing unit definition for squid – some questions
Hi, I'm slowly porting init scripts of software I use to systemd unit files. It is generally straight-forward, but today Squid made me wonder. Squid is web-caching daemon (proxy) with some pecularities. It stores the cache of the internet in some directories on disk. To paralleize access, it is recommended to define separate cache_dir for each hard disk. Also, squid likes 2-level deep folder structure in each cache_dir, to implement simple hashing and deal with lesser filesystems. Populating each defined cache_dir can be slow operation, therefore it is not done automatically. Fedora's squid script checks if cache_dir is empty and if so, run the command to create folder hierarchy. This “populate” command is great candidate for separating into its own unit, squid-populate.service, required by main squid.service and using negated ConditionDirectoryNotEmpty=. As I mentioned, there could be more than one cache_dir definition. For each one, separate squid-populate.service should be created, using @ instances. (BTW, we cannot grep-out all the directories from squid.conf, administrator needs to repeat cache_dir configuration in systemd units). Now the question: how should requires be defined? Which is better way? 1) should squid.service explicitly require squid-populate@/var/spool/squid/cache1.service, …cache2.service etc? This means that administrator would need to modify main squid.service when adding more cache_dirs or 2) should each instance define itself as required by squid.service? If so, how to do it? This behaviour makes adding directories simpler. Nb. I consider using unit generator parsing squid.conf an overkill for this task :) Second issue, cascading timeouts. Let's say squid-populate.service has TimeoutSec=3m, because it may be slow. Main squid.service has standard 1m timeout. What happen when I run systemctl start squid.service with empty cache directory? squid-populate.service will be started and may work for, let's say, 2 minutes. Will systemctl timeout after 1m? Or after 3m+1m? In future squid may be socket-activable. If population is needed, will the timeout for connection be 3m (populate) + 1m (squid itself) + 1m (socket timeout) = 5m ? Side observation: systemd has only one timeout for start and stop. Squid's sysv script defines short timeout for start and much longer for stop (because squid waits for open connection to end when closing). -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl-- Baron Vladimir Harkonnen ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to Test systemd on F14?
On Thu, Dec 30, 2010 at 05:04:25PM +0100, Michał Piotrowski wrote: Hi, AFAIK systemd is not supported on F14 and now nobody cares. I think that if you want to test it on F14 you need to build a few things: - systemd - initscripts - udev - kernel (perhaps) Not really. I'm using systemd on most of my F14 machines. Packaged version (v10) is quite old and prone to bugs, but it works most of the time. Original poster problems can be solved by installing sysvinit-systemd package instead of sysvinit-upstart. -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd hangs for several minutes on shutdown if it gets service force-reload request
On Fri, Jan 14, 2011 at 09:19:34AM +0100, Tollef Fog Heen wrote: ]] Lennart Poettering | What I wonder in this case, why vnstat.service/reload appears to hang | in this case? The job itself fails during startup (initscript is | disabled, so it gets indirect request from ifup and does nothing): | | Does this probelm still exist? | | Most likely this is simply an ordering deadlock: systemd executes | something that asks systemd to execute something else which however is | order after the first unit. That is is not really fixable. At least I | am have no idea what we could do about this. We should at least print out/log what's happening when this happens. Slightly related, it'd be really nice if we could have a way to poke systemd to dump state. I'm trying to track down a problem where boot takes a while, and spawning extra shells and using serial consoles kinda work, but it doesn't work that great. “ SIGUSR2 When this signal is received the systemd manager will log its complete state in human readable form. The data logged is the same as printed by systemctl dump. ” -- Tomasz Torcz 72-| 80-| xmpp: zdzich...@chrome.pl 72-| 80-| ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd hangs for several minutes on shutdown if it gets service force-reload request
On Fri, Jan 14, 2011 at 12:44:46PM +0100, Tollef Fog Heen wrote: ]] Tomasz Torcz Hi, | “ SIGUSR2 |When this signal is received the systemd manager will log its complete |state in human readable form. The data logged is the same as printed by systemctl dump. | ” This is useful. It'd be even more useful if I could just hit a key combination and make it happen. Do you know if I can? There kbrequest.target which is started when systemd receives SIGWINCH or you press Alt+↑ on console. I suppose you could drop and enable following unit: --- [Service] ExecStart=/bin/systemctl list-jobs StandardOutput=tty [Install] WantedBy=kbrequest.target --- and “systemctl enable …” it. Now pressing alt-up during boot should show you what jobs systemd is waiting for. Likewise, you can change ExecStart= to “/bin/kill -USR2 1” (or “/bin/systemctl dump”) to have full dump. But full dump is probably less useful. -- Tomasz Torcz ,,If you try to upissue this patchset I shall be seeking xmpp: zdzich...@chrome.pl an IP-routable hand grenade.'' -- Andrew Morton (LKML) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd restart patch
On Thu, Feb 03, 2011 at 09:35:55PM +0100, Michael Biebl wrote: 2011/2/3 Cristian Patrascu cristian.patra...@windriver.com: So, for these last two features I created a patch, which adds two more options for a .service : - RestartRetries=n (where n is the number of restart retries) - ExecPostRestarts=/some/cmd (where the command /some/cmd will be executed after restart retries are finished). I think the name of this option is not very descriptive and imho it could be useful in a more general way. What do you think about using ExecStartOnFailure=/some/cmd (send an email or what not) Isn't “OnFailure=send-email-to-admin.service” sufficent? -- Tomasz Torcz God, root, what's the difference? xmpp: zdzich...@chrome.pl God is more forgiving. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] /usr on separate file system
On Thu, Mar 03, 2011 at 06:45:21PM +0100, Lennart Poettering wrote: On Thu, 03.03.11 17:58, Tollef Fog Heen (tfh...@err.no) wrote: ]] Lennart Poettering | To boot a system, enough must be present on the root partition to | mount other filesystems. This includes utilities, configuration, | boot loader information, and other essential start-up data. /usr, | /opt, and /var are designed such that they may be located on other | partitions or filesystems. | | Well, turns out no distro really follows the spec here, do they? Given the number of Debian people I see running with separate /usr, I believe it works just fine there and while it's a supported configuration I'll patch the warning out of the Debian systemd packages, at least. Well, it's of course up to you guys what you do there. But it's a promise you are making there that you cannot keep. If you want to support /usr on a separate partition then you'd need to do all the work and move the PCI and USB databases to /, move libatasmart, fix udisks, fix D-Bus and so on. The fact that most these things fail relatively gracefully should not mislead you to believe that everything worked fine. Things still fail, just not in a big gigantic atomic explosion scenario. I don't get it. What during the boot (before /usr is mounted) require pci.db, usb ids, why udisks would be started? I understand that full desktop session need access to those, but we are talking about short window before starting system and mounting /usr. What will break? Are the some udev rules needing mapping between PCI ID and a name? Anything else? (BTW, “yum remove libatasmart” suggest removal of udisks, nautilus, gvfs, evolution and some GNOME parts. Nothing related to boot). -- Tomasz Torcz 72-| 80-| xmpp: zdzich...@chrome.pl 72-| 80-| ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] /usr on separate file system
On Thu, Mar 03, 2011 at 05:39:03PM -0300, Pablo Hess wrote: Not supporting a separate /usr would be a major setback for systemd, IMO. Separate /usr has nothing to do with systemd. It just the way current distribution work. Systemd is just a messenger, don't shot it because of friendly reminder. -- Tomasz Torcz 72-| 80-| xmpp: zdzich...@chrome.pl 72-| 80-| ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Improve boot-time of systemd
On Wed, Apr 20, 2011 at 02:43:36AM +0200, Lennart Poettering wrote: On Fri, 18.03.11 13:40, Gustavo Sverzut Barbieri (barbi...@profusion.mobi) wrote: On Fri, Mar 18, 2011 at 10:52 AM, Andrey Borzenkov arvidj...@mail.ru wrote: On Fri, Mar 18, 2011 at 12:35 PM, fykc...@gmail.com fykc...@gmail.com wrote: Hi all, We did a series boot-time tests of systemd, and found some interesting things: (Note the tests were performed on a laptop with a 4-core mips cpu, AMD RS780 chipset, 2GB Memory, rotate harddisk with ext4 filesystem, debian squeeze, Linux 2.6.36 with fanotify enabled, systemd-v20, only boot to console.) 1. What can readahead affect boot-time? Sadly observed negative affect -- boot-time increases at least 1s. From subjective feelings (no real measurements) I confirm it. I noticed it as well, even with my Macbook Pro i7 with 8Gb RAM and 128SSD using btrfs. Note that btrfs is actually not particularly fast when mounting. We do serialization of fsck on rotating media already. This might be something that fixes itself as soon as the btrfs mounting isn't as slow anymore as it currently is. You can speed up btrfs mounting with free space caching. Right now it is enable with -o space_cache mount option. But beware: there was some problem identified when free space reporting. I am not sure if fix went to .38 and .39-rc already. -- Tomasz Torcz God, root, what's the difference? xmpp: zdzich...@chrome.pl God is more forgiving. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] X socket with logind and poly-instantiated /tmp
Hi, I noticed following message in logs today: systemd-logind[15652]: Linked /tmp/.X11-unix/X0 to /run/user/tomek/X11/display. I wonder how this is going to work with poly-instantiated /tmp dirs, as described at http://fedoraproject.org/wiki/Infrastructure/FedoraPeopleConfig#polyinstantiated_tempdirs ? I use poly-/tmp on most of my important machines. By virtue of being important, they do not run latest development version of systemd ;) -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl-- Baron Vladimir Harkonnen ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] question
On Mon, Sep 12, 2011 at 01:44:30PM +0100, Sérgio Basto wrote: hi on this report https://bugzilla.redhat.com/show_bug.cgi?id=696815 I ask how I know , if a service is enable or disable at startup ? and for different start up levels , since # systemctl list-unit-files | grep ava avahi-daemon.service enabled avahi-daemon.socket enabled or # systemctl is-enabled avahi-daemon.service enabled chkconfig --list| grep -i av don't return the info. chkconfig do not now about native services -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] question
On Mon, Sep 12, 2011 at 03:34:48PM +0200, Reindl Harald wrote: Am 12.09.2011 15:32, schrieb Tomasz Torcz: On Mon, Sep 12, 2011 at 02:08:35PM +0100, Sérgio Basto wrote: Thanks for reply but fails here on Fedora 15: You need newer version of systemd than packaged for F15 yes and this is a problem release F15 with systemd and not update with missing things at release time! Sorry, but you missed with your whining by half a year, or even more. systemd is in development for almost two years now. It was available in Rawhide during F13 time, then it was available in F14 before it got included in F15. That's plenty of time to state concerns or even fix the issues you encounter. It's open source after all, scratch your own itch, you got what you paid for, etc. -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] question
On Mon, Sep 12, 2011 at 05:49:21PM +0100, Sérgio Basto wrote: On Mon, 2011-09-12 at 15:47 +0200, Tomasz Torcz wrote: On Mon, Sep 12, 2011 at 03:34:48PM +0200, Reindl Harald wrote: Man , what version do we need ? 'list-unit-files' was added in 729e3769c32242bbba26ea96900be005d52ce438 in July. It should be in v31. I got systemd-26-9.fc15.x86_64 Latest packaged for Fedora is systemd-35-1.fc16. As I said, version maintained in F15 is not recent enough. -- Tomasz Torcz 72-| 80-| xmpp: zdzich...@chrome.pl 72-| 80-| ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd - consolekit, spice-vdagent questions
On Wed, Sep 14, 2011 at 04:26:20PM +0200, Hans de Goede wrote: Currently the linux spice-vdagent is using ConsoleKit to figure out (for the first seat, it assumes a vm is single seat): 1) Which session is active (including notification of when this changes) 2) Which session each session agent process belongs too It needs this to figure out to which session agent process to send copy/paste requests for copy paste between the active session in the guest and the client. What are the equivalents for these now ? Hans, I think docs at http://www.freedesktop.org/wiki/Software/systemd/multiseat could be useful for you. -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] modprobe in service file
On Tue, Nov 08, 2011 at 10:14:03AM -0500, Michael D. Berger wrote: In my /etc/init.d/filterDaemon, I have, for example, modprobe -q ip_queue How do I do this in a new filterDaemon.service? You can use ExecStartPre=, but nowadays it's better to load the modules at bootup, by echo ip_queue /etc/modules-load.d/filterDaemon.conf (or by shipping this file ine package). -- Tomasz TorczTo co nierealne -- tutaj jest normalne. xmpp: zdzich...@chrome.pl Ziomale na życie mają tu patenty specjalne. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] can not systemctl enable rc.local in final fc16
On Mon, Nov 14, 2011 at 05:00:46AM -0500, floydsm...@aol.com wrote: I can not systemctl enable rc.local.service in final fc16 - error is: Failed to issue method call: No such file or directory Proper name is rc-local.service (with '-'). BTW, it would be much better if you create proper units for stuff you put in rc.local. -- Tomasz Torcz God, root, what's the difference? xmpp: zdzich...@chrome.pl God is more forgiving. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [Linux-ima-user] [PATCH 2/2] main: added support for loading IMA custom policies
On Thu, Feb 16, 2012 at 12:30:31PM -0200, Gustavo Sverzut Barbieri wrote: On Thu, Feb 16, 2012 at 11:38 AM, Roberto Sassu roberto.sa...@polito.it wrote: the reason for which the loading of IMA policies has been placed in the main Systemd executable is that the measurement process performed by IMA should start as early as possible. Otherwise, in order to build the 'chain of trust' during the boot process from the BIOS to software applications, it is required to measure those components loaded before IMA is initialized with other means (for example from the boot loader). Then I wonder: why not make an ima-init binary that: - does ima_setup() - exec systemd || upstart || ... this way you only have to audit this very small file and not systemd itself, it's very early and so on. Isn't that a job for initramfs? -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Socket-Activation
On Fri, Mar 30, 2012 at 02:48:03PM +0100, Ayoub Arfaoui wrote: How to patch a service to be socket-activable ? http://0pointer.de/blog/projects/socket-activation.html http://0pointer.de/blog/projects/socket-activation2.html -- Tomasz TorczTo co nierealne -- tutaj jest normalne. xmpp: zdzich...@chrome.pl Ziomale na życie mają tu patenty specjalne. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Is there a general inittab entry replacement available?
On Tue, May 22, 2012 at 09:27:34PM +0200, Joachim Banzhaf wrote: As it happens I also like IBM DB2 a lot (for other reasons). DB2 is closed source (I hope you dont stop reading now) and it installs an inittab entry. fmc:2345:respawn:/opt/ibm/db2/V10.1/bin/db2fmcd #DB2 Fault Monitor Coordinator You know that this does no longer work. Inittab is a very old, very widely spread concept so I have hope you even have thought about porting something like this in a generic way already and I just failed to find it? inittab is not used on general Linux for few years already. Most distros switched to upstart some time ago, upstart isn't parsing inittab (except for default runlevel). The line you provided translates to following systemd unit: /etc/systemd/system/fmc.service --- [Unit] Description=DB2 Fault Monitor Coordinator [Service] ExecStart=/opt/ibm/db2/V10.1/bin/db2fmcd Restart=always [Install] WantedBy=multi-user.target --- It simple, but let me describe it: fmc becomes service name - fmc.service 2345 is not directly mappable. There are no runlevels with systemd. multi-user.target is roughly equivalent of all system services started. If your inittab had 1 here (single user), you would want WantedBy=rescue.target in [Install] session. Please see man systemd.special for description of other targets. respawn becomes Restart=always The command itself lands in ExecStart=; because this command do not daemonize (requisite for being in inittab), you can skip Type= declaration. It will default to simple. You can put comment in Description field. You are now only systemctl enable fmc.service away of emulating inittab. Above unit definition is really simple but fully replaces inittab entry. However, please look at man pages of systemd.exec and systemd.service. You will find many way to augment this unit (various limits, chroot, running as specific user, group etc). -- Tomasz Torcz 72-| 80-| xmpp: zdzich...@chrome.pl 72-| 80-| ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Is there a general inittab entry replacement available?
On Tue, May 22, 2012 at 10:06:04PM +0200, Joachim Banzhaf wrote: Thanks for your answers, all three of them! Am 22.05.2012 21:42, schrieb Tomasz Torcz: Restart=always AFAIK SysV init restarts the service on failures immediatelly for some times, then uses a delay of some minutes before it retries, which seems sensible. If I understand systemd.service man correctly this is not possible? You are looking for StartLimitInterval=, StartLimitBurst= in that manpage. -- Tomasz Torcz 72-| 80-| xmpp: zdzich...@chrome.pl 72-| 80-| ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to interact with `systemd --user`?
On Thu, Jun 14, 2012 at 10:29:47PM +0300, Ciprian Dorin Craciun wrote: Hello all! I want to play a little with systemd, but first I want to use it in a sandbox user, thus I start it (as non-root) from a console with I'd rather suggest installing Fedora or other systemd-enabled distribution in virtual machine and playing with that. You will get used to systemd much easier. -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl-- Baron Vladimir Harkonnen ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] cpufrequtils considered useless (was: systemd unit files for Debian based systems)
On Tue, Jun 19, 2012 at 11:42:10AM +0200, Paul Menzel wrote: Nah, really, cpufrequtils should just go away. People should use the kernel APIs right away. alright looking into why `cpufrequtils` is installed on my system I now know the reasons. The frequency(?) modules are not loaded automatically and therefore the init.d script shipped by `cpufrequtils` is needed. Without the appropriate modules loaded – in my case `powernow_k8` – no power saving features of the CPU are available. So how is this supposed to work out of the box? This was fixed in kernel (1.4. x86 CPU driver autoprobing): http://kernelnewbies.org/Linux_3.4#head-9df4e508cb97f4e138c590b9ccff3e0eda6cc7fc -- Tomasz Torcz God, root, what's the difference? xmpp: zdzich...@chrome.pl God is more forgiving. pgpIsdgNJrpyX.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] 'Offline System Updates' examination
On Thu, Jun 21, 2012 at 12:45:02PM +0200, Lennart Poettering wrote: On Thu, 21.06.12 12:31, Antonio Trande (anto.tra...@gmail.com) wrote: BTRFS ? Will 'Offline Updates' be available only with BTRFS ? Nope. But on btrfs we'll make a snapshot of the old system state. On non-btrfs we won't. Maybe BTRFS will be the default filesystem in Fedora 18, therefore all that make sense. If i use EXT4, are snapshots (that are a guarantee if update fails) not available ? This automation of updates could be difficulty manageable. Snapshots only make sense really on CoW filesystems such as btrfs, and they are not supported on ext4. That means the extra safety net that is a snapshot will only be available on btrfs, and not on ext4, but the snapshot is really just the cherry on top, not a must-have. yum-plugin-fs-snapshot has logic to do snapshots both on btrfs and on LVM level. btrfs is a better option, though. -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Q: IPv6-only setup - get rid of 127.0.0.1
On Thu, Jun 21, 2012 at 04:42:54PM +0400, Alexey I. Froloff wrote: Hi, I am running F17 in IPv6-only network (behind NAT64 gateway) and would like to get rid of 127.0.0.1 address from lo interface. Please, don't tell me, that this would break lots of stone-aged software, because such configuration works for about a year already in non-RH distro. I can't find who sets inet 127.0.0.1/8 scope host address to lo interface. Commented out the IPADDRESS in ifcfg-lo - no result. systemd sets this very early during boot. -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Documentation about upstreaming unit files
On Fri, Jun 29, 2012 at 05:52:45PM +0200, Paul Menzel wrote: 1. What license should the unit files have? The one of the upstream project? Probably yes. Unit files are trivial in most cases. 2. Should the unit files be put in a directory `systemd/`? 3. Do the distributions install the file to the correct directory `/lib/systemd/system/` or is the upstream build system supposed to do that? man 7 daemon contains example autotools snippets, which install unit files to directory pointed by pkg-config. Those snippets detects non-systemd distributions and do not install units then. Some changes may be needed to parse unit definitions and substitute for example paths in accordance with --prefix= and --*dir= parameters during build. 4. What should upstream do if the service files differ for distributions? Try very hard to minimize delta and optimally have only one unit for all distributions. This may require implementing configuration file support and build-time declaration of its default location. -- Tomasz TorczTo co nierealne -- tutaj jest normalne. xmpp: zdzich...@chrome.pl Ziomale na życie mają tu patenty specjalne. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH 2/2] systemd: enabling/disabling template units
On Tue, Jul 03, 2012 at 12:04:40PM +0200, Michal Sekletar wrote: Makes possible to enable/disable instance of units and should resolve Many thanks for implementing this! -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [RFC] VTs for multiple seats
On Mon, Jul 09, 2012 at 10:27:35PM +0200, Lennart Poettering wrote: (Also, I think Plymouth should be replaced by the system compositor as well, as a side note) Side not to side note: Ubuntu people seem to agree with you: http://summit.ubuntu.com/uds-q/meeting/20429/desktop-q-system-compositor/ -- Tomasz Torcz God, root, what's the difference? xmpp: zdzich...@chrome.pl God is more forgiving. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Integration with Buildroot (uclibc-based runtime): patches suggested
On Fri, Jul 13, 2012 at 09:19:01AM -0400, Dmitry Golubovsky wrote: Buildroot's toolchain by default provides runtime environment based on uclibc [2] which lacks certain functionality systemd depends upon, so I had to develop some workarounds. In particular, functions like execvpe, posix_fallocate, mkostemp, and %ms format are not implemented. These patches are applicable against the v186 snapshot. I would like to hear from the systemd dev team whether there is an interest in uclibc integration; we can work together on finalizing these patches. If there is no such interest, patches will remain with Buildroot as they currently are. Wouldn't it be better (and beneficial to others) to implement missing functionality in uclibc? -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. xmpp: zdzich...@chrome.pl Your routes will be aggreggated. -- Alex Yuriev ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-nspawn should not require getent initgroups
On Sun, Sep 14, 2014 at 01:44:21PM +0200, Marco d'Itri wrote: It was implemented in glibc 2.15, so it is not available in Debian stable and RHEL 6 at least, and systemd-nspawn --user does not work. Those distribution won't see systemd implemented during their lifetime, so this is not a problem PS. You hijacked a thread. -- Tomasz Torcz ,,If you try to upissue this patchset I shall be seeking xmpp: zdzich...@chrome.pl an IP-routable hand grenade.'' -- Andrew Morton (LKML) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] centralized logs
On Mon, Sep 15, 2014 at 02:47:12PM +0300, Mihamina Rakotomandimby wrote: Hi all I currently manage several virtual machines which are not using systemd because it's not default yet. I've set them up to remote log to a RSyslog central point. But, the future releases of my favorite distribution are going the systemd way. I must keep them logging to a central logging, as it is now. You can keep using rsyslog. It has journal-reading input modules. Would you know how to? For native journal soulution, please evalute systemd-journal-upload. -- Tomasz TorczOnly gods can safely risk perfection, xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Prioritize the /etc configuration over /usr/lib also with .include
On Tue, Sep 16, 2014 at 03:16:12PM +0200, Zbigniew Jędrzejewski-Szmek wrote: On Tue, Sep 16, 2014 at 01:21:30PM +0200, Pavel Raiskup wrote: Hi, consider the situation that admin has /etc/systemd/system/a.service, which includes via .include the /usr/lib/systemd/system/a.service. Then in our case there exists also packaged /usr/lib/systemd/system/a.service.d/ with existing drop-in. In this case - the setup from /etc/ is beaten by drop-in files from /usr/lib. Reproducer is in Red Hat Bugzilla [1]. I would expect that parser starts at /etc/systemd/*/*.service, which invokes the .include ~ so '/usr/lib/*/*.service is parsed, then '/usr/lib/*/*.service.d', then remaining part of '/etc/*/*.service is parsed and as the last step, the '/etc/*/*.service.d/' dropins should be done. This would change the way that drop-ins work. Your model is not necessarily worse, but dropins have been the advertised way to do overiddes for a while, and we cannot simply revert the order in which they are applied. At least not without a very good reason which would make it worth to upset existing users. I'd like to ask why dropins are packaged in the first placed? Do you (Pavel) have some variants of the package that share common unit file? -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz.. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd service for kinit
On Wed, Sep 17, 2014 at 08:53:30PM +0200, Günther J. Niederwimmer wrote: Am Mittwoch, 17. September 2014, 21:01:09 schrieb Andrei Borzenkov: В Wed, 17 Sep 2014 18:46:45 +0200 Günther J. Niederwimmer g...@gjn.priv.at пишет: Hello, Am Mittwoch, 17. September 2014, 15:35:44 schrieb Andrei Borzenkov: On Wed, Sep 17, 2014 at 2:44 PM, Günther J. g...@gjn.priv.at wrote: Hello, I have a problem with kinit (krb5) before on my old system this works with a cron file @reboot root /usr/bin/sleep 120 /usr/bin/kinit -k host/. now with systemd I can't say why, the extra characters don't work @reboot Could you explain what do you mean? One of - @reboot is not accepted by cron I mean this is the problem ;) And why do you think it is caused by systemd? with my older system without systemd all works and I can't found in the cron doc that any change are make. But this is not my question. Is it possible to create a kinit.service that works on the same way? You seem to be mixing cron problems with systemd. Anyway, you may approximate wanted behaviour by creating kinit.timer with OnBootSec=2m (or OnStartupSec=, check man systemd.timer) and kinit.service, type oneshot, and ExecStart with your kinit invocation. Please note, this may work 99% but it's not proper solution. You should tie services depending on your kinit with proper Requires= and After=. -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [uml-devel] Timed out waiting for device dev-disk-by...
On Tue, Sep 30, 2014 at 08:27:36PM +0200, Thomas Meyer wrote: Am Montag, den 29.09.2014, 22:20 +0200 schrieb Richard Weinberger: On Mon, Sep 29, 2014 at 8:29 PM, Thomas Meyer tho...@m3y3r.de wrote: Hi, I get a timeout in the Fedora 21 alpha: [ TIME ] Timed out waiting for device dev-disk-by\x2duuid-008af19d\x2d2562\x2d49bd\x2d8907\x2d721ea08f3e14.device. What exactly makes the device unit go into the state active/plugged? This is a boot of the Fedora 21 alpha under user mode linux. Some more info about the above systemd wait (with systemd.log_level=debug and DEBUG_KOBJECT) Systemd starts and installs a job for each device tagged with systemd: Sep 30 18:07:58 localhost systemd[1]: Installed new job dev-ubdb3.device/start as 34 Sep 30 18:07:58 localhost systemd[1]: Installed new job systemd-fsck@dev-ubdb3.service/start as 35 Sep 30 18:07:58 localhost systemd[1]: Enqueued job initrd.target/start as 1 Sep 30 18:07:58 localhost systemd[1]: Loaded units and determined initial transaction in 837.189ms. Sep 30 18:07:58 localhost systemd[1]: Received SIGCHLD from PID 32 (n/a). Device unit is waiting: Sep 30 18:07:58 localhost systemd[1]: Expecting device dev-ubdb3.device... udev coldplug: Sep 30 18:08:02 localhost systemd[360]: Executing: /bin/dracut-pre-trigger Sep 30 18:08:02 localhost dracut-pre-trigger[360]: rd.dm=0: removing DM RAID activation Sep 30 18:08:02 localhost systemd-udevd[358]: starting version 215 Sep 30 18:08:02 localhost dracut-pre-trigger[360]: rd.md.imsm=0: no MD RAID for imsm/isw raids Sep 30 18:08:03 localhost dracut-pre-trigger[360]: rd.md.ddf=0: no MD RAID for SNIA ddf raids Sep 30 18:08:03 localhost dracut-pre-trigger[360]: rd.md=0: removing MD RAID activation Sep 30 18:08:04 localhost kernel: kobject: 'alarmtimer' (930ef220): kobject_uevent_env Sep 30 18:08:04 localhost kernel: kobject: 'alarmtimer' (930ef220): fill_kobj_path: path = '/devices/platform/alarmtimer' Sep 30 18:08:04 localhost kernel: kobject: 'uml-blkdev.1' (605a1700): kobject_uevent_env Sep 30 18:08:04 localhost kernel: kobject: 'uml-blkdev.1' (605a1700): fill_kobj_path: path = '/devices/platform/uml-blkdev.1' Sep 30 18:08:04 localhost kernel: kobject: 'ubdb' (8c030480): kobject_uevent_env Sep 30 18:08:04 localhost kernel: kobject: 'ubdb' (8c030480): fill_kobj_path: path = '/devices/platform/uml-blkdev.1/block/ubdb' Sep 30 18:08:04 localhost kernel: kobject: 'ubdb1' (93205838): kobject_uevent_env Sep 30 18:08:04 localhost kernel: kobject: 'ubdb1' (93205838): fill_kobj_path: path = '/devices/platform/uml-blkdev.1/block/ubdb/ubdb1' Sep 30 18:08:04 localhost kernel: kobject: 'ubdb2' (93205638): kobject_uevent_env Sep 30 18:08:04 localhost kernel: kobject: 'ubdb2' (93205638): fill_kobj_path: path = '/devices/platform/uml-blkdev.1/block/ubdb/ubdb2' Sep 30 18:08:04 localhost kernel: kobject: 'ubdb3' (93205438): kobject_uevent_env Sep 30 18:08:04 localhost kernel: kobject: 'ubdb3' (93205438): fill_kobj_path: path = '/devices/platform/uml-blkdev.1/block/ubdb/ubdb3' Check the udev database at this moment. In my understanding, to have device deemed ready by systemd, two things must happen for device entry: – TAGS variable must contain ”systemd” – SYSTEMD_READY must be ”1” I don't have UML installation handy to check, but maybe there is missing rule? Rule which is supposed to flip SYSTEMD_READY to ”1”? Some default devices are tagged in 99-systemd.rules; if UML-specific devs are missing, please send a patch. -- Tomasz TorczFuneral in the morning, IDE hacking xmpp: zdzich...@chrome.plin the afternoon and evening. - Alan Cox ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [uml-devel] Timed out waiting for device dev-disk-by...
On Fri, Oct 03, 2014 at 07:14:51PM +0200, Thomas Meyer wrote: Hmm ... one of common reason for such problems recently was missing CONFIG_FHANDLE in kernel configuration. Could you verify that all required kernel options are set in your case? Hi Andrei, Thanks for this tip! My kernel config did indeed miss the CONFIG_FHANDLE option. After recompiling the kernel, the devices where automatically detected by systemd! Does systemd log a message somewhere about this missing kernel option? Did I miss the relevant notice in the log messages? You have missed README. -- Tomasz Torcz ,,(...) today's high-end is tomorrow's embedded processor.'' xmpp: zdzich...@chrome.pl -- Mitchell Blank on LKML ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] I wonder… why systemd provokes this amount of polarity and resistance
On Thu, Oct 23, 2014 at 05:00:04PM +, dennis.mur...@wipro.com wrote: One thing I would like to point out, on the project website there is NO mailing list for advocacy. The comment this is for technical email only use a different ML is for all purposes just a brush off. If the project would create an advocacy mailing list it would go a long way toward segregating the email. Who would participate in such list? I wouldn't, personally. I prefer technical discussions. -- Tomasz Torcz Morality must always be based on practicality. xmpp: zdzich...@chrome.pl-- Baron Vladimir Harkonnen ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [question] networkd: Any support for hooks?
On Thu, Oct 02, 2014 at 08:36:10AM +0200, Lennart Poettering wrote: On Wed, 01.10.14 21:36, Cameron Norman (camerontnor...@gmail.com) wrote: Hello, ifupdown [1], NetworkManager, and WICD all support hooks for when a network interface is configured or deconfigured (before and after these actions). Are there any plans to support something along these lines? If so, what will that look like? If there are no plans, how do networkd's developers feel about adding the feature (will not merge, or will accept patches, etc.) ? Can you be more specific what precisely you intend to hook in there? I'd really prefer if we could find different solutions for the common usecases. Example: I'd like to add interface to proper firewalld zone. Ideally it could be done by networkd itself (it just one dbus call: addInterface(in s zone, in s interface, …) based on new Zone=string setting in .netdev file. Hook can determine which zone interface should belong to and call firewall-cmd --zone=zone --add-interface=interface -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] instantiated services set up
On Tue, Nov 04, 2014 at 08:56:48PM +0100, Jan Včelák wrote: Hi! OK. I will remove the syslog. But I will have to keep network.target for now as we support non-Linux systems as well. Adding support for rtnl or IP_FREEBIND would mean duplicating a lot of code... probably. Note that invoking IP_FREEBIND is just a single setsockopt() line... You are right. We enabled IP_FREEBIND after all. (And we also added IP_BINDANY and IPV6_BINDANY on FreeBSD to achieve the same behavior.) On the other hand, we cannot give the administrator proper feedback when the daemon is configured incorrectly. If you need, you can first try binding without IP_FREEBIND. If it fails, you can print Configured address (xxx) not available yet, enable IP_FREEBIND and call bind() again. -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] xinetd REMOTE_IP (feature request)
On Thu, Nov 13, 2014 at 01:53:12PM -0500, Fisher, Charles J. (Top Echelon)
wrote:
The xinetd server from previous versions of RedHat defined a REMOTE_IP
environment variable.
I realize that I can extract that data with the following code:
{
struct sockaddr_in thisconn;
int thislen = sizeof(thisconn);
getpeername( /* STDIN */ 0, thisconn, thislen);
printf(%s\n, inet_ntoa(thisconn.sin_addr));
}
...but it would be nice if the behavior matched xinetd.
You can do it in shell by parsing instance name embedded
in /proc/self/cgroup
--
Tomasz Torcz RIP is irrevelant. Spoofing is futile.
xmpp: zdzich...@chrome.pl Your routes will be aggreggated. -- Alex Yuriev
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH 2/2] networkd: integrate LLDP
On Sun, Nov 23, 2014 at 10:15:10AM +0530, Susant Sahani wrote: This patch integrates LLDP with networkd. In Fedora, we already have LLDP receiver/broadcaster – ladvd. It has this neat feature of abusing ifAlias by putting endpoint name there. This gives port information right at ip l output: 3: enp5s0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 10:78:d2:cc:7e:b0 brd ff:ff:ff:ff:ff:ff alias connected to Core2-3b-24p (Fa0/7) Would it be possible to implement this in networkd? -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. xmpp: zdzich...@chrome.pl Your routes will be aggreggated. -- Alex Yuriev ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] make systemd service takes cpu exclusively
On Thu, Nov 27, 2014 at 12:44:50PM +, Cao, XinX wrote: But it’s very strange, for I can’t find “sd_notify” or “sd_notifyf” in my program, but seems that notify type can still work. So are there any other functions able to do this ? Thanks~~ Are you sure it's working? If you specify notify for non-notify program, it will start OK, but will get killed after 90s (by default). -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH 2/2] networkd: integrate LLDP
On Sun, Nov 23, 2014 at 02:17:18PM +0100, Tom Gundersen wrote: On Sun, Nov 23, 2014 at 12:01 PM, Tomasz Torcz to...@pipebreaker.pl wrote: On Sun, Nov 23, 2014 at 10:15:10AM +0530, Susant Sahani wrote: This patch integrates LLDP with networkd. In Fedora, we already have LLDP receiver/broadcaster – ladvd. It has this neat feature of abusing ifAlias by putting endpoint name there. This gives port information right at ip l output: 3: enp5s0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 10:78:d2:cc:7e:b0 brd ff:ff:ff:ff:ff:ff alias connected to Core2-3b-24p (Fa0/7) Would it be possible to implement this in networkd? Definitely possible. However, any suggestions on how to avoid stepping on the toes of other abusers of ifAlias, or is ladvd simply ignoring this? I've enabled it in Fedora's ladvd almost three years ago, and received no bugreports about breaking any other software. ladvd does not take any special precautions. I think it would be safe to refrained from changing ifAlias if: - ifAlias is already set, AND - it doesn't start with connected to -- Tomasz TorczFuneral in the morning, IDE hacking xmpp: zdzich...@chrome.plin the afternoon and evening. - Alan Cox ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] SIT tunnel does not work
On Thu, Dec 04, 2014 at 04:01:40PM +0100, Tom Gundersen wrote: Hi Tomasz, Sorry to dig up such an old thread, but I just made some changes to the sit handling, and at least for me it works now. This is the config I'm currently using: he.netdev ---8- [NetDev] Name=he Kind=sit [Tunnel] Remote=222.333.444.555 TTL=255 ---8- (you probably don't need the source routing stuff, but that's what I was testing). Do you still see problems with this on your end with current git? Hi Tom, I got it working with systemd-216-7.fc21.x86_64 and configuration very similar to what you have provided. I only have additional Local=… setting in [Tunnel] section of he.netdev. It works, but configuration is counter-intuitive for me. The need to put Tunnel=… in physical device (wlp3s0) configuration file is perplexing. First, iproute2 does not require physical device when configuring SIT tunnels. Second, I had to enter IP address twice - first for the physical device, second time for Local= in tunnel config. It's kinda redundant, but I see you have no Local= settings, so maybe the redundancy was fixed. And third, I was expecting ”he” device to be top-level, independent device just like ”wlp3s0” is. Right now the Tunnel= keyword makes it dependant on physical device, which is more limiting and contrary to what iproute2 made me used to in the past 15 years. -- Tomasz TorczTo co nierealne -- tutaj jest normalne. xmpp: zdzich...@chrome.pl Ziomale na życie mają tu patenty specjalne. pgpTCMadnoGPB.pgp Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
