Re: CURRENT: Panic VERIFY(!zil_replaying(zilog, tx)) failed (and crashing)

In message <20230409161436.5412f...@thor.intern.walstatt.dynvpn.de>, FreeBSD Us er writes: > Am Sun, 9 Apr 2023 14:37:03 +0200 > Mateusz Guzik schrieb: > > > On 4/9/23, FreeBSD User wrote: > > > Today, after upgrading to FreeBSD 14.0-CURRENT #8 main-n262052-0d4038e301 > 2b: > > > Sun Apr 9 > >

Re: documentation nit / TERMINFO in ncurses man pages

On Fri, Apr 07, 2023 at 09:51:30AM -0500, Dan Mack wrote: > > I recently logged into one of my FreeBSD systems from an alacritty terminal. > FreeBSD didn't have a termcap entry for alacritty so I generated one with > tic and all was well. However, I noticed the following issues with the > TERM*

Re: [FUSEFS] File close() failures relating to attempted atime update

Thanks for the head's up. Hopefully I'll be able to look at it later this week. On Mon, Apr 10, 2023 at 4:40 PM Jamie Landeg-Jones wrote: > > There is a replicable problem with file closing on fusefs, since > 0bade34633f997c22f5e4e0931df0d534f560a38, Alan Somers > 2021-11-29 01:53:31 + > >

[FUSEFS] File close() failures relating to attempted atime update

There is a replicable problem with file closing on fusefs, since 0bade34633f997c22f5e4e0931df0d534f560a38, Alan Somers 2021-11-29 01:53:31 + It appears to be related to attempting to update atime on a file you don't have write-access to. I've posted much more details, and a potential fix to