previous: >>108023158#define __NR_shmget 29https://man7.org/linux/man-pages/man2/shmget.2.htmloh man, any time i see system v in a man page, i start to get nervous. shm_segsz looks like seggs and sounds like seggsy, though, which is kind of amusing. same goes for SHMALL, eheh...in general, i really like the concept of shared memory outside of the context of threads. i just don't really like threads, thoughrelevant resources: man manman syscallshttps://man7.org/linux/man-pages/https://linux.die.net/man/https://elixir.bootlin.com/linux/https://elixir.bootlin.com/musl/https://elixir.bootlin.com/glibc/
#define __NR_shmget 29
shm_segsz
man man
man syscalls
"allocates a System V shared memory segment"is that different than a regular shared memory segment? or the same thing? I guess I only know /dev/shm
Now, this one really is legacy garbage that needs to die.Either use mmap on files in /tmp, pass memfds between your programs, or use wrappers around the above (e.g. shm_open)
>>108032241that is a very good question
bampu
>shmget
>>108032139so what happens when systemd is replaced by some other system manager in the future? Do we just get stuck with syscalls like these, adding bloat and complexity to the kernel?
dropkick chao to the poolmegaton punch chao off the cliffhurl chao egg at the oceanbully chao
>>108038178be nice to poor chao ;___;
