[systemd-devel] FYI: github PRs run tests on IBM zSystems now
Hello all, We have a second architecture besides x86_64 for github PR integration tests now: IBM zSeries (aka s390x, fka zSeries or System Z). So we now have coverage of big-endian as well. We can only run a few integration tests there though, as on this architecture we don't have real QEMU yet, so we are limited to container tests. But we still at least run make check, booting, and networkd. https://github.com/systemd/systemd/pull/2777 is an example PR. I'll continue to monitor the PRs to check for flakiness or infrastructure problems. Once that stabilizes, we can also consider adding x86 so that we cover 32 bit too. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] howto systemd restart one network device
Am Mon, 29 Feb 2016 22:59:17 -0800 schrieb J Decker : > well that was the search > > after everything is up how do I restart a single device so it will > work in the meantime... I usually do "systemctl restart systemd-networkd" which probably restarts all devices. This worked for me all the time. Maybe something like: $ systemctl restart sys-subsystem-net-devices-enp5s0.device ^^ put your device here Found by "systemctl | fgrep enp" However, "systemctl show ..." indicates it doesn't support doing that. -- Regards, Kai Replies to list-only preferred. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] After update from 208->229 can't get calendar timers to work :-\
HI I updated systemd from 208 to 229 and since then I can’t get working my calendar timers. I spent hours trying to understand why it is not working…. Running „systemctl list-timers” for not working calendar timer shows: ——— NEXT LEFTLAST PASSEDUNITACTIVATES ….. Wed 2016-03-02 02:25:00 CET 5h 15min left n/a n/a mythtv-epg-grab-and-load.timer mythtv-epg-grab-and-load.service ….. ——— NEXT and LEFT times are shown correctly - so it looks systemd correctly reads .timer unit. All timers are symlinked in /etc/systemd/system/timers.target.wants But corresponding service is never started. mythtv-epg-grab-and-load.timer unit is following: ——— [Unit] Description=Timer for periodic EPG grabing and loading to DB [Timer] OnCalendar=Mon,Wed,Fri *-*-* 02:25:00 # OnCalendar=*-*-* 11:05:00 AccuracySec=1us Unit=mythtv-epg-grab-and-load.service [Install] WantedBy=timers.target ——— mythtv-epg-grab-and-load.service ——— [Unit] Description=@Periodic EPG grabing and loading to DB After=mysqld.service mythbackend.service [Service] User=mythtv Group=mythtv Type=oneshot Nice=19 IOSchedulingClass=2 IOSchedulingPriority=7 ExecStart=/usr/bin/wg++/grab-and-load-epg.sh [Install] WantedBy=default.target ——— May somebody hint me where issue is? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] FYI: github PRs run tests on IBM zSystems now
On Tue, 01.03.16 19:44, Martin Pitt (martin.p...@ubuntu.com) wrote: > Hello all, > > We have a second architecture besides x86_64 for github PR integration > tests now: IBM zSeries (aka s390x, fka zSeries or System Z). So we > now have coverage of big-endian as well. > > We can only run a few integration tests there though, as on this > architecture we don't have real QEMU yet, so we are limited to > container tests. But we still at least run make check, booting, and > networkd. https://github.com/systemd/systemd/pull/2777 is an example PR. > > I'll continue to monitor the PRs to check for flakiness or > infrastructure problems. Once that stabilizes, we can also consider > adding x86 so that we cover 32 bit too. Thanks a ton! This is excellent work! Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] howto systemd restart one network device
yes restart repeatedly does the same thing and doesn't work On Tue, Mar 1, 2016 at 10:49 AM, Kai Krakow wrote: > Am Mon, 29 Feb 2016 22:59:17 -0800 > schrieb J Decker : > >> well that was the search >> >> after everything is up how do I restart a single device so it will >> work in the meantime... > > I usually do "systemctl restart systemd-networkd" which probably > restarts all devices. This worked for me all the time. > > Maybe something like: > > $ systemctl restart sys-subsystem-net-devices-enp5s0.device > ^^ > put your device here > > Found by "systemctl | fgrep enp" > > However, "systemctl show ..." indicates it doesn't support doing that. > fgrep he // he is in 'ethernet' but he-tunnel is the .netdev I want to start [code] sys-devices-pci:00-:00:19.0-net-eno1.device loaded active plugged Ethernet Connection I217-LM sys-subsystem-net-devices-eno1.device loaded active plugged Ethernet Connection I217-LM httpd.service loaded active running Apache Web Server kmod-static-nodes.service loaded active exitedCreate list of required static device nodes for the current kernel systemd-fsck@dev-disk-by\x2duuid-50a189be\x2d1ec4\x2d4efc\x2db575\x2d7396e7923413.service loaded active exitedFile System Check on /dev/disk/by-uuid/50a189be-1ec4-4efc-b575-7396e7923413 systemd-fsck@dev-disk-by\x2duuid-d55e3257\x2d76bb\x2d49a5\x2da9ff\x2d076b0559369e.service loaded active exitedFile System Check on /dev/disk/by-uuid/d55e3257-76bb-49a5-a9ff-076b0559369e systemd-fsck@dev-disk-by\x2duuid-fec23492\x2d4be8\x2d4c03\x2d9349\x2d9ee06ab2c5ff.service loaded active exitedFile System Check on /dev/disk/by-uuid/fec23492-4be8-4c03-9349-9ee06ab2c5ff man-db.timer loaded active waiting Daily man-db cache update LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. [/code] and just blindly trying it... systemctl restart sys-subsystem-net-devices-he-tunnel.netdev Failed to restart sys-subsystem-net-devices-he-tunnel.netdev.service: Unit sys-subsystem-net-devices-he-tunnel.netdev.service not found. > -- > Regards, > Kai > > Replies to list-only preferred. > > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
