Indeed, I landed there later after my reply. I'm disappointed that it
was never resolved, but I did add a service unit which works
perfectly.
-
[Unit]
Description=Set system clock from hardware clock
After=systemd-modules-load.service
[Service]
Type=oneshot
ExecStart=/sbin/hwclock
On Thu, 12 Mar 2020 17:35:16 -0400
"Kevin P. Fleming" wrote:
> Thanks, I agree. I could some up with something which ran timedatectl
> to set the system time from the RTC, but the hwclock tool is already
> there for that purpose.
>
> I'll need to investigate why this script exits without making
Thanks, I agree. I could some up with something which ran timedatectl
to set the system time from the RTC, but the hwclock tool is already
there for that purpose.
I'll need to investigate why this script exits without making any
changes when systemd is running; either the authors expected some
https://www.freedesktop.org/software/systemd/man/systemd.network.html#KeepConfiguration=
From: systemd-devel
Date: Thursday, 12 March 2020 at 7:56 PM
To: Systemd
Subject: [systemd-devel] Networkd - how to augment an already configured
interface
Hi,
for a rather complex tunneling setup on a
On Thu, Mar 12, 2020 at 7:13 AM Kevin P. Fleming wrote:
> Prior to systemd, with the 'hwclock' package installed, a udev rule
> would trigger reading of the RTC and setting the system clock when
> /dev/rtc0 appeared. With systemd running, the script run by that udev
> rule is suppressed, it
Hi,
for a rather complex tunneling setup on a system that uses
systemd-networkd and OpenVPN, I am trying to use networkd to augment the
Interface that has been configured by OpenVPN.
In OpenVPN, a daemon is started with a service unit, which connects to a
remote side and creates a tunX interface
I've got some Debian Buster systems (so using the Debian systemd
package 241-7), which have battery-backed RTCs. However the driver for
these RTCs is loaded as a module, not built into the kernel. As a
result the kernel's feature of reading the RTC to set the system clock
is not available.
Prior
On Thu, Mar 12, 2020 at 8:29 AM Michael Chapman wrote:
>
> On Thu, 12 Mar 2020, Jędrzej Dudkiewicz wrote:
> [...]
> > And one more question: what is systemd-timedated? It seems that is
> > exactly same thing, but I don't think this is true?
>
> It's the DBus service that most bits of timedatectl
Hello,
I am on Ubuntu 18.04.2, and I have systemd version 237. I have some common tasks
which need to happen prestart and poststop which I have moved to a
script. All unit
files look like:
StandardOutput=file:/var/log/my-.log
ExecStartPre=/path/to/helper.sh -t prestart -u
On Thu, 12 Mar 2020, Jędrzej Dudkiewicz wrote:
[...]
> And one more question: what is systemd-timedated? It seems that is
> exactly same thing, but I don't think this is true?
It's the DBus service that most bits of timedatectl talk to. timedatectl
doesn't modify system configuration directly.
>>> Mantas Mikulenas schrieb am 11.03.2020 um 17:52 in
Nachricht
<12133_1583945545_5E691749_12133_1276_1_CAPWNY8XJRN7-U15LmgpgXbqBeFPWJokEDM==EXd
5hc-adn...@mail.gmail.com>:
> Well, are you asking about the *source* port or about the *destination*
> port? There are two on every UDP packet.
>
>
11 matches
Mail list logo
