On Tue, Mar 29, 2016 at 8:41 AM, Konstantin Khomoutov wrote:
According to manual pages on my Linux system, 4 syscalls and
accompanying data types cover the whole semaphores thing.

So, this task appears to be tractable.
If you're using existing semaphores created by another process this is
true, but if you want to create your own semaphore you'll need to be
able to call sem_open(3) (for named semaphores; there are other
methods for closing, unlinking, creating unnamed semaphores, etc.).

I assume this is what he's asking about, and it would probably make
sense to stick something like that in x/sys/unix.


A full list (I think?) would include:

- sem_open(3)
- sem_wait(3)
- sem_post(3)
- sem_close(3)
- sem_unlink(3)
- sem_init(3)
- sem_destroy(3)

Sam Whited
pub 4096R/54083AE104EA7AD3

You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 5 of 9 | next ›
Discussion Overview
groupgolang-nuts @
postedMar 29, '16 at 8:34a
activeMay 12, '16 at 1:05a



site design / logo © 2022 Grokbase