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
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 i
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
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
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,