control: severity -1 important

Hello Joerg,

>I think if virtualbox-guest-utils has problems with ntp, virtualbox-
>guest-utils should fix this problem instead of uninstalling a standard
>program used for years.
>
>On the other hand I find it impossible that neither a reference to the
>deletion of ntp in the changelog is present nor in the NEWS.


* Conflict with ntp services due to systemd hack removed.
(Closes: #873263)

>I have absolutely nothing against that virtualbox-guest-utils use its
>own time synchronization, but system-wide only if no other time server
>runs.
>It is also incomprehensible for users to install virtualbox-guest-utils 
>as a time server.
>Therefore, I reopen the bug again.


this is nothing against NTP, problem is just that simply vbox can't use it.

VBox has to use its internal implementations of various tools, by kernel 
modules,
e.g. usb bridging, copy-paste, file drag and drop, vboxvideo, and so on.

Simply, the current tools can't cope with virtualbox needs because they aren't 
aware
of it (and they shouldn't be).

If you want to use ntp, just remove virtualbox-guest-utils and use it?

e.g. VBoxService can cope with a misconfigured network, or with other sort of 
issues, e.g.
when no connectivity is found, it will get the time from the host, and sync it 
with the guest.

It is superior than NTP, just because it has been created to cope with such 
special cases

So, I can lower the conflict to ntp, but what will happen with two NTP servers 
running together
on the same machine?

This might be a big source of troubles, and btw systemd-timesyncd was already 
configured to be silenced
when vbox is in place.

G.

Reply via email to