Hello André,
André Hartmann [2016-12-09 10:46 +0100]:
> To sum up again what I actually want to achive:
>
> I want to use NTP after bootup by default, but in case no NTP is available,
> the user should be able to set the date and time by hand
> with timedatectl. But timedatectl refuses to do so,
On Fri, 9 Dec 2016, André Hartmann wrote:
Hi Michael,
Am 09.12.2016 um 12:43 schrieb Michael Chapman:
On Fri, 9 Dec 2016, Michael Chapman wrote:
[...]
> You will need to use the .service extension on at least the first of
> those links. systemd will only consider links in that directory
Hi Michael,
Am 09.12.2016 um 12:43 schrieb Michael Chapman:
On Fri, 9 Dec 2016, Michael Chapman wrote:
[...]
You will need to use the .service extension on at least the first of
those links. systemd will only consider links in that directory that
have valid unit names. (I'm pretty sure the
On Fri, Dec 09, 2016 at 10:46:51AM +0100, André Hartmann wrote:
> Hi Martin,
>
> thanks for keeping our dialog alive :)
>
> To sum up again what I actually want to achive:
>
> I want to use NTP after bootup by default, but in case no NTP is available,
> the user should be able to set the date
On Fri, 9 Dec 2016, Michael Chapman wrote:
[...]
Your'e right, I had a typo. But after checking again, I discovered the
following:
cat /etc/systemd/system/sysinit.target.wants/systemd-timesyncd
(empty)
But systemctl status systemd-timesyncd says active (running)
The link structure is
On Fri, 9 Dec 2016, André Hartmann wrote:
Hi Michael,
Am 09.12.2016 um 10:25 schrieb Michael Chapman:
On Thu, 8 Dec 2016, André Hartmann wrote:
[...]
> Which confuses me is the inconsistency between
> "systemctl status systemd.timesyncd" and "timedatectl status":
>
> # systemctl status
Hi Michael,
Am 09.12.2016 um 10:25 schrieb Michael Chapman:
On Thu, 8 Dec 2016, André Hartmann wrote:
[...]
Which confuses me is the inconsistency between
"systemctl status systemd.timesyncd" and "timedatectl status":
# systemctl status systemd.timesyncd
* systemd.timesyncd.service
Hi Martin,
thanks for keeping our dialog alive :)
To sum up again what I actually want to achive:
I want to use NTP after bootup by default, but in case no NTP is
available, the user should be able to set the date and time by hand
with timedatectl. But timedatectl refuses to do so, if "NTP
On Thu, 8 Dec 2016, André Hartmann wrote:
[...]
Which confuses me is the inconsistency between
"systemctl status systemd.timesyncd" and "timedatectl status":
# systemctl status systemd.timesyncd
* systemd.timesyncd.service
Loaded: not-found (Reason: No such file or directory)
Active:
Hello André,
André Hartmann [2016-12-08 9:28 +0100]:
> My main problem is that I cannot disable NTP by setting
> the link to /dev/null as the root partition is read-only.
Well, of course you can't change the image configuration after
building it -- you need to disable the service in the image
Hi Martin,
Am 04.12.2016 um 17:48 schrieb Martin Pitt:
Hello André,
André Hartmann [2016-12-01 11:20 +0100]:
In other words: once this symlink is valid, you cannot invalidate it by
make it a dangling symlink, you have to remove it. Can somebody confirm this
observation?
Not a dangling one,
Hello André,
André Hartmann [2016-12-01 11:20 +0100]:
> In other words: once this symlink is valid, you cannot invalidate it by
> make it a dangling symlink, you have to remove it. Can somebody confirm this
> observation?
Not a dangling one, but you should be able to make a symlink in /etc
Hi Martin,
Am 01.12.2016 um 10:20 schrieb Martin Pitt:
Hello André,
André Hartmann [2016-12-01 9:50 +0100]:
So I naively created the following link structure (which works):
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service ->
/mnt/writeable/systemd-timesyncd ->
Hello André,
André Hartmann [2016-12-01 9:50 +0100]:
> So I naively created the following link structure (which works):
>
> /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service ->
> /mnt/writeable/systemd-timesyncd ->
> /lib/systemd/system/systemd-timesyncd.service
>
> But if I
14 matches
Mail list logo
