On 19/11/2020 14:54, John Nelson via wsjt-devel wrote:
Hi Bill,
I have just had a reply from W4 about info sysctl. This is the same as that in
use now - dated 2007. However, the line marked BUG might explain what has
been discovered in the present case.
— John G4KLA
BUGS
If loadable kernel modules are used to introduce additional kernel func-
tionality and sysctls to manage that functionality, sysctl.conf may be
processed too early in the boot process to set those sysctls.
Hi John,
my days of understanding anything about the mach kernel are long passed,
but I would be surprised if shared memory was managed by a kext. Are we
sure that a sysctl.conf with the necessary systctl parameter changes is
not being read on reboot? The fact that the parameters can be using
sysctl after the system has started make me suspicious that something is
wrong with the sysctl.conf file itself.
This command should show the success or failure of sysctls since the
last boot:
sudo log show --process 0 --last boot | grep sysctl
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
