pfSense

The change only applies to the PHP used directly by pfSense, as they are set with config.inc.

For testing you can use

<?php
require_once("/etc/inc/config.inc");

echo ini_get("memory_limit");

?>

That inc will be loaded automatically inside pfSense. Also there is no need for a reboot for it to take effect.

Got it and checked, working as expected.

Could this also be adapted to use a disk swap? That way it could have an option to use and allocate fixed disk storage if needed or required. Kind of Like a reverse MS-DOS ramdisk if you are old enough to remember using this within MS-DOS 5 I think it was.

is the Path Strip Count 2 for the patch?

Jonathan Lee wrote in #note-12:

I added your patch set this to 512mb and I am still getting that snort error for active rules

Crash report begins. Anonymous machine information:

arm64
14.0-CURRENT
FreeBSD 14.0-CURRENT #1 plus-RELENG_23_05_1-n256108-459fc493a87: Wed Jun 28 04:25:15 UTC 2023 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_05_1-main/obj/aarch64/0P4W6joa/var/jenkins/workspace/pfSense-Plus-snapshots-23_05_1-main/source

Crash report details:

PHP Errors:
[04-Aug-2023 09:30:42 US/Pacific] PHP Fatal error: str_ireplace(): Cannot use output buffering in output buffering display handlers in /usr/local/www/csrf/csrf-magic.php on line 161

No FreeBSD crash data found.

That error doesn't seem to be related to memory issues, so this patch wouldn't affect it.

Jonathan Lee wrote in #note-10:

Could this also be adapted to use a disk swap? That way it could have an option to use and allocate fixed disk storage if needed or required. Kind of Like a reverse MS-DOS ramdisk if you are old enough to remember using this within MS-DOS 5 I think it was.

Right now, this just adds a GUI interface for the existing PHP memory limit settings. In almost all cases, the default values are sufficient.

I don't see there being much of a need to allocate disk space as well, but you could theoretically create a swap partition and increase this value to the point that it would start using that. That's definitely not tested nor recommended, though.

Jonathan Lee wrote in #note-15:

Thanks for the reply,

just to confirm the is the Path Strip Count 2 for your patch?

That should be correct. Some updates are being made to the code still, so that's delaying the merge. That original patch is still functional, though.

Tested on

23.09-DEVELOPMENT (amd64)
built on Sat Aug 26 17:37:15 UTC 2023
FreeBSD 14.0-ALPHA2

It's merged in and functioning as expected. I'll wait for others to test as well, since I made the changes.

Chris W wrote in #note-19:

Systems with 1GB or less of RAM show a negative number as the hinted maximum adjusted value. The screenshot is taken from a virtual machine with 512 MB RAM (and with 1GB, the value becomes 128 to -62).

Thanks for catching that. I have submitted a merge request to handle those cases more elegantly.
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/1065

Should allow the user to fill in the PHP memory according to the total memory capacity of the server

still seeing a negative number suggested for the higher limit on system with <1gb RAM running 23.09-DEVELOPMENT-amd64-20230909-1856

Jordan G wrote in #note-22:

still seeing a negative number suggested for the higher limit on system with <1gb RAM running 23.09-DEVELOPMENT-amd64-20230909-1856

The new patches weren't merged in yet, should be in the next build.

New patches just merged.

What is recommended for SG-2100MAX with 23.05.01 in use I can't remember I was using 128 I think but you guys are showing 512 now half a gb?