Re: cwm: keep pointer within window on maximize/fullscreen toggle

On Thu, Apr 08, 2021 at 03:35:33AM +0200, Klemens Nanni wrote: > This scratch has been itching me for far too long and concerns the > funcionality behind those cwm(1) default bindings: This fixes one of the few problems I have with cwm. Works well for me. ok kmos --Kurt >CM-f

Re: monotonic time going back by wrong skews

On Wed, Apr 07, 2021 at 06:18:40PM +0200, Mark Kettenis wrote: > > From: Scott Cheloha > > Date: Wed, 7 Apr 2021 10:25:04 -0500 > > > > > On Apr 6, 2021, at 07:49, Paul Irofti wrote: > > > > > The diff is obviously fine. But it is still a heuristic with no real > > motivation except

cwm: keep pointer within window on maximize/fullscreen toggle

This scratch has been itching me for far too long and concerns the funcionality behind those cwm(1) default bindings: CM-fToggle full-screen mode of current window. CM-mToggle maximization of current window. CM-equalToggle vertical

Re: vmd: spurious VM restarts

On Wed, Apr 07, 2021 at 07:47:28PM -0400, Dave Voutila wrote: > > Thomas L. writes: > > >> > Thomas: I looked at your host dmesg and your provided vm.conf. It > >> > looks like 11 vm's with the default 512M memory and one (minecraft) > >> > with 8G. Your host seems to have only 16GB of memory,

Re: vmd: spurious VM restarts

Thomas L. writes: >> > Thomas: I looked at your host dmesg and your provided vm.conf. It >> > looks like 11 vm's with the default 512M memory and one (minecraft) >> > with 8G. Your host seems to have only 16GB of memory, some of which >> > is probably unavailable as it's used by the integrated

Re: vmd: spurious VM restarts

> > Thomas: I looked at your host dmesg and your provided vm.conf. It > > looks like 11 vm's with the default 512M memory and one (minecraft) > > with 8G. Your host seems to have only 16GB of memory, some of which > > is probably unavailable as it's used by the integrated gpu. I'm > > wondering if

Re: iwm(4) A-MSDU support

Hi Stefan, just tested today with my other laptop (Dell Latitude 7400): iwm0 at pci0 dev 20 function 3 "Intel Dual Band Wireless AC 9560" rev 0x30, msix iwm0: hw rev 0x310, fw ver 34.3125811985.0, address 60:f2:62:06:61:f2 ...against an Ubiquity UniFi AC AP Pro. Before patch: Up: Conn: 1

Re: vmd: spurious VM restarts

On Wed, Apr 07, 2021 at 09:23:14AM -0400, Dave Voutila wrote: > > Dave Voutila writes: > > > Mike Larkin writes: > > > >> On Wed, Apr 07, 2021 at 12:22:23AM +0200, Thomas L. wrote: > >>> On Tue, 6 Apr 2021 14:28:09 -0700 > >>> Mike Larkin wrote: > >>> > >>> > On Tue, Apr 06, 2021 at 09:15:10PM

Re: vmd: spurious VM restarts

On Wed, Apr 07, 2021 at 07:26:41AM -0400, Dave Voutila wrote: > > Mike Larkin writes: > > > On Wed, Apr 07, 2021 at 12:22:23AM +0200, Thomas L. wrote: > >> On Tue, 6 Apr 2021 14:28:09 -0700 > >> Mike Larkin wrote: > >> > >> > On Tue, Apr 06, 2021 at 09:15:10PM +0200, Thomas L. wrote: > >> > > On

Re: apmd/apm: propagate failure to apm, make apm report failure

On Wed, Apr 07, 2021 at 12:35:12AM +0200, Jeremie Courreges-Anglas wrote: > And those functions could return zero/errno, this saves a few more > lines. ok? Even better, OK kn

Re: monotonic time going back by wrong skews

> From: Scott Cheloha > Date: Wed, 7 Apr 2021 10:25:04 -0500 > > > On Apr 6, 2021, at 07:49, Paul Irofti wrote: > > > The diff is obviously fine. But it is still a heuristic with no real > motivation except for this particular ESXi VM case. So my question > about why we choose

Re: monotonic time going back by wrong skews

> On Apr 6, 2021, at 07:49, Paul Irofti wrote: > The diff is obviously fine. But it is still a heuristic with no real motivation except for this particular ESXi VM case. So my question about why we choose the minimum instead of the median or the mean has not been answered.

Re: rpki-client http client and bind to address

On Wed, Apr 07, 2021 at 12:55:50PM +0200, Claudio Jeker wrote: > When -b is used rpki-client should bind to that address for outgoing > connections. The http code does that but only warns if a bind call fails > but try the connect none the less. This is different from other network > tools (nc,

Re: rpki-client rrdp merge repo fix

On Wed, Apr 07, 2021 at 12:50:15PM +0200, Claudio Jeker wrote: > In some cases unlink reports 'no such file or directory' when the RRDP > repository is merged at the end of a RRDP sync. > The problem is that some deleted files are in the temporary location and > not part of the real repo. Because

Re: vmd: spurious VM restarts

Dave Voutila writes: > Mike Larkin writes: > >> On Wed, Apr 07, 2021 at 12:22:23AM +0200, Thomas L. wrote: >>> On Tue, 6 Apr 2021 14:28:09 -0700 >>> Mike Larkin wrote: >>> >>> > On Tue, Apr 06, 2021 at 09:15:10PM +0200, Thomas L. wrote: >>> > > On Tue, 6 Apr 2021 11:11:01 -0700 >>> > > Mike

Re: vmd: spurious VM restarts

Mike Larkin writes: > On Wed, Apr 07, 2021 at 12:22:23AM +0200, Thomas L. wrote: >> On Tue, 6 Apr 2021 14:28:09 -0700 >> Mike Larkin wrote: >> >> > On Tue, Apr 06, 2021 at 09:15:10PM +0200, Thomas L. wrote: >> > > On Tue, 6 Apr 2021 11:11:01 -0700 >> > > Mike Larkin wrote: >> > > > Anything

rpki-client http client and bind to address

When -b is used rpki-client should bind to that address for outgoing connections. The http code does that but only warns if a bind call fails but try the connect none the less. This is different from other network tools (nc, ftp, telnet). So change this to a real error. -- :wq Claudio Index:

rpki-client rrdp merge repo fix

In some cases unlink reports 'no such file or directory' when the RRDP repository is merged at the end of a RRDP sync. The problem is that some deleted files are in the temporary location and not part of the real repo. Because of this if unlink return ENOENT then try the alternate location. While