aboutsummaryrefslogtreecommitdiff
path: root/devel/p5-Data-SExpression
diff options
context:
space:
mode:
authorAlexander Leidinger <netchild@FreeBSD.org>2025-08-29 07:44:59 +0000
committerAlexander Leidinger <netchild@FreeBSD.org>2025-08-29 08:07:34 +0000
commita3fbcaec539824a635d1bd53a2508fafae06ec6a (patch)
tree57aaed3aac4b69f66be99e14cfdb19d45eddbfc2 /devel/p5-Data-SExpression
parent1e4dfb851e8af3f44d2c2c7f99d1f6eeca7b4f64 (diff)
www/apache24: make the start script service jails readyHEADmain
The setup I've chosen is to allow ipv4/ipv6 access. It does not allow to use sysv IPC in a jail. If you want to use this possibility, the config would need to be changed to "net_basic sysvipc" instead. More advanced use cases may need different service jail options. The config can be overridden in rc.conf. See also: https://docs.freebsd.org/en/books/handbook/jails/#service-jails https://docs.freebsd.org/en/articles/rc-scripting/#rcng-service-jails Some notes: - There are special apache24_limits_* stuff which is different from the name_limits stuff as part of the rc framework. - The limits part in the precmd will probably not work in a service jail, as the start command will be executed in a jail and the precmd outside the jail. - While the patch is taking the profiles into account, it may fail when the jail is started, as the name of the service jail is derived from the name of the rc script (assuming "profiles" means different instances of apache are started for each profile). The tomcat/oauth2-proxy/openhab ports use a way to have different instances of the software running in parallel which is based upon the name of the rc script (via links to the original rc script). That way works well with service jails. Approved by: maintainer timeout PR: 279494
Diffstat (limited to 'devel/p5-Data-SExpression')
0 files changed, 0 insertions, 0 deletions