Interesting discussion regarding sig_atomic_t, volatile & stuff. It seems I
opened a can of worms. Sorry :-)
Anyway here are the references I had read when suggesting this change:
C89:
- http://port70.net/~nsz/c/c99/n1256.html#7.14p2
CERT C Coding Standard:
-
https://wiki.sei.cmu.edu/confluen
Keep the global variables as defaults that apply to all nfsds and allow (at
least some subset) to be overridden inside the net jails if some things need to
be changed from the defaults?
- Peter
On Fri, Nov 25, 2022, 4:24 PM Rick Macklem mailto:rick.mack...@gmail.com>> wrote:
> Hi,
>
> bz@ has
I just noticed that a couple of my 12.2-RELEASE-p4 running servers have… 8263,
14474 and 3831 defunct subprocesses from syslogd and also seems to have stopped
writing to the log files… When I tried to kill syslogd on a fourth server (with
some X000 defunct processes) the machine panic’ed and reb
After upgrading FreeBSD 12.2 in order to get the fix from 'FreeBSD Security
Advisory FreeBSD-SA-21:12.libradius’ sudo with pam_radius has started to fail
for us. It correctly seems to communicate with the RADIUS server (used to
trigger MFA authentication, so I get an authentication popup in the
I vote for this.
+1
- Peter
> On 14 May 2021, at 01:02, Rick Macklem wrote:
>
> Hi,
>
> I believe that NFSv4.1 and NFSv4.2 are now mature in freebsd-current/main.
> I also believe that NFSv4.1/4.2 is a better protocol than NFSv4.0.
> (In particular, the sessions mechanism for "exactly once R
Suggestion:
Add a check for sysctl vfs.nfsd.server_min_nfsvers and if set to 4 or higher -
automatically enable the “-R” option.
- Peter
> On 20 Oct 2020, at 02:56, Rick Macklem wrote:
>
> Hi,
>
> I've put a patch up on phabricator that adds a new option to mountd
> which disables use of rp
to use the getnanouptime() call to get a “clock” to look
for (it’s used in print_uptime()). As long as the clock isn’t stopped at this
time in the shutdown sequence atleast :-)
*Time to write some code and test this* :-)
- Peter
> On 29 Nov 2019, at 22:09, Enji Cooper wrote:
>
>
>&
I’ve been looking into the “kernel looks to be hung at reboot” problem at bit.
Adding a lot of printf() calls to the relevant parts it looks like it actually
isn’t hung but busy unmounting filesystems (which we have thousands of),
flushing disk caches, calling registered callbacks and stuff and
