On Saturday, 18 March 2017 05:09:59 UTC+11, cooloutac wrote:
> On Thursday, March 16, 2017 at 11:26:48 PM UTC-4, Drew White wrote:
> > On Friday, 17 March 2017 11:36:25 UTC+11, Jean-Philippe Ouellet wrote:
> > > As for changing the NTP server used, feel free to submit patches.
> >
> > If I was
On Friday, 17 March 2017 11:36:25 UTC+11, Jean-Philippe Ouellet wrote:
> Qubes only runs an NTP client in the ClockVM (sys-net) and syncs all
> other domains via qrexec services, so your claim about NTP traffic
> coming from multiple VMs on a default system is false.
>
> As for changing the NTP
On Friday, 17 March 2017 11:36:25 UTC+11, Jean-Philippe Ouellet wrote:
> As for changing the NTP server used, feel free to submit patches.
If I was to submit patches, they wouldn't be in Python Code. So I can't submit
any changes because my applications aren't written in Python.
--
You
On Friday, 17 March 2017 11:36:25 UTC+11, Jean-Philippe Ouellet wrote:
> Qubes only runs an NTP client in the ClockVM (sys-net) and syncs all
> other domains via qrexec services, so your claim about NTP traffic
> coming from multiple VMs on a default system is false.
>
> As for changing the NTP
Qubes only runs an NTP client in the ClockVM (sys-net) and syncs all
other domains via qrexec services, so your claim about NTP traffic
coming from multiple VMs on a default system is false.
As for changing the NTP server used, feel free to submit patches.
--
You received this message because
On Friday, 17 March 2017 11:03:13 UTC+11, Drew White wrote:
> On Monday, 13 March 2017 19:48:19 UTC+11, Jean-Philippe Ouellet wrote:
> > On Mon, Mar 13, 2017 at 12:54 AM, Drew White wrote:
> > > On Monday, 13 March 2017 15:02:42 UTC+11, Jean-Philippe Ouellet wrote:
> > >>
On Monday, 13 March 2017 19:48:19 UTC+11, Jean-Philippe Ouellet wrote:
> On Mon, Mar 13, 2017 at 12:54 AM, Drew White wrote:
> > On Monday, 13 March 2017 15:02:42 UTC+11, Jean-Philippe Ouellet wrote:
> >> From my quick reading of the source and observations of my systems,
On Mon, Mar 13, 2017 at 12:54 AM, Drew White wrote:
> On Monday, 13 March 2017 15:02:42 UTC+11, Jean-Philippe Ouellet wrote:
>> From my quick reading of the source and observations of my systems,
>> that appears to be exactly how it is implemented right now.
>
> In other
On Monday, 13 March 2017 15:02:42 UTC+11, Jean-Philippe Ouellet wrote:
> On Sun, Mar 12, 2017 at 10:59 PM, Drew White wrote:
> > Question: Why does it not work properly then?
>
> Answer: Must be because of something you changed on your system.
>
> It *does* appear to work
On Sun, Mar 12, 2017 at 10:59 PM, Drew White wrote:
> Question: Why does it not work properly then?
Answer: Must be because of something you changed on your system.
It *does* appear to work properly by default, confirmed by not seeing
the NTP traffic you describe on two
On Monday, 13 March 2017 13:44:17 UTC+11, Jean-Philippe Ouellet wrote:
> On Sun, Mar 12, 2017 at 10:24 PM, Drew White wrote:
> > On Monday, 13 March 2017 12:36:55 UTC+11, Jean-Philippe Ouellet wrote:
> >> On Sun, Mar 12, 2017 at 9:19 PM, Drew White
On Sun, Mar 12, 2017 at 10:24 PM, Drew White wrote:
> On Monday, 13 March 2017 12:36:55 UTC+11, Jean-Philippe Ouellet wrote:
>> On Sun, Mar 12, 2017 at 9:19 PM, Drew White wrote:
>> > I want to set the NTP protocol to target the parent VM and on the
On Sun, Mar 12, 2017 at 9:19 PM, Drew White wrote:
> Hi folks,
Hi,
> I want to set the NTP protocol to target the parent VM and on the NetVM or
> Sys-Firewall have that as the NTP server that feeds everything under it.
No, you don't want that.
> Thus only one VM calls
Hi folks,
I want to set the NTP protocol to target the parent VM and on the NetVM or
Sys-Firewall have that as the NTP server that feeds everything under it.
Thus only one VM calls the external source at a lesser interval to do the
requests.
How, in this system, do I perform this to get that
14 matches
Mail list logo