Corrections:
1. Those *other* modules (the ones missing from your list).
2. You want the *former*, not the latter. Sounds like you want jails with
startup scripts.
‐‐‐ Original Message ‐‐‐
On Saturday, February 13, 2021 5:12 PM, JB
wrote:
> > So I guess Linux service is restarted by "
‐‐‐ Original Message ‐‐‐
On Saturday, February 13, 2021 2:25 AM, Thomas Mueller
wrote:
> So I guess Linux service is restarted by "service linux restart"?
# service | grep List
-l List all scripts in /etc/rc.d and /usr/local/etc/rc.d
# service -l | grep ux
linux
The `service' co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #13 from Alex S ---
(In reply to Alex S from comment #12)
OK, just for completeness, FreeBSD — pretty accurate, Linux — only for initial
thread: https://gist.github.com/shkhln/af421368a36727926ad9103e8f59b455.
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #12 from Alex S ---
(In reply to Conrad Meyer from comment #11)
Rampant copy-pasting finally got me, ROFL.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #11 from Conrad Meyer ---
You need to use /proc/getpid()/maps — your most recent demo is showing cat’s
memory map.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #10 from Alex S ---
(In reply to Conrad Meyer from comment #8)
I noticed neither Linux nor FreeBSD actually bothers with accurate
stack mappings in /proc/self/map. About multiple threads Linux's
documentation plainly states "[s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #9 from Conrad Meyer ---
I think this may have been introduced in r320317 (19bd0d9c85cc):
Implement address space guards.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #8 from Conrad Meyer ---
Sure, we could also just try to hide that entry. I'm honestly not sure what
the point of the explicit --- mapping is for.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #7 from Conrad Meyer ---
In exec, we map the stack with vm_map_stack() with rlim_cur (I think); in
vm_map_stack, we set the init_ssize with MIN(sysctl kern.sgrowsiz, rlim_cur).
kern.sgrowsiz is 128kB.
There's a comment about
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #6 from Alex S ---
(In reply to Conrad Meyer from comment #5)
Yep, that's pretty much it. Do you think it makes sense to just hide that
entry?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337
--- Comment #5 from Conrad Meyer ---
Ok, here's what's going on:
Our rlimit value (cur) is fine; same as glibc (8MB).
Glibc is parsing /proc/self/maps to limit the pthread "stack size" based on
adjacent mappings, *which it assumes cannot
from Damjan Jovanovic :
> On Sat, Feb 13, 2021 at 6:31 AM Thomas Mueller wrote:
> > from JB:
> > > If it's just a local directory, you can use `sysctl' to tell the kernel
> > what the emulation path is:
> > > sysctl compat.linux.emul_path=/foo/bar
> > > Then restart
12 matches
Mail list logo
