previous: >>108170938#define __NR_listen 50https://man7.org/linux/man-pages/man2/listen.2.htmlwell... more sockets again, huh? but we'll be done after this week, and then we get to some really fun syscallsthe notes section in this manpage is pretty nice. listing out a series of steps like this is always helpful for understanding (at least to me)relevant 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_listen 50
man man
man syscalls
>listing out a series of steps like this is always helpful for understanding (at least to me)I feel like this too. Syscall man pages are really hit or miss in that regard, either they are actually helpful with examples and good explanations, or they are just there, so there is a man page for it.
Hey
bump for effortpost
bampu
are you feeling better, OP?>>108182163a lot of manpages make an effort to include a valid C programme, which I don't really think is necessary.Just include the 3 lines that are semantically necessary, and leave it to very obvious context how the rest of the programme would have to look like
>>108180698>listenhttps://www.youtube.com/watch?v=XVTysXvNYDA
>>108185201yes, thankfully!! lots of work to catch up on since i was out, though
>>108180698the part I find the hardest to understand is the polling. Yeah, duh the socket is listening but what does that even mean?All I know is a socket file descriptor gets written to (?) and at some point it's the kernel that tells the socket fd, hey bro there is someone connecting
>>108180698dumb kot
>>108186036many such cases !
>>108180698not interested in loonix or c but it's still a neat idea for threads
