Alan Somers cf037972ea libcasper: document that most libcasper functions are not thread-safe ... And neither are most libcasper services' functions, because internally they all use cap_xfer_nvlist. cap_xfer_nvlist sends and then receives data over a unix domain socket and associated with the cap_channel_t argument. So absent synchronization, two threads may not use the same cap_channel_t argument or they risk receiving the other's reply. MFC after: 2 weeks Sponsored by: Axcient Reviewed by: oshogbo Differential Revision: https://reviews.freebsd.org/D42928		2023-12-08 09:22:39 -07:00
..
cap_syslog.3	libcasper: document that most libcasper functions are not thread-safe	2023-12-08 09:22:39 -07:00
cap_syslog.c	Remove $FreeBSD$: one-line .c pattern	2023-08-16 11:54:42 -06:00
cap_syslog.h	Remove $FreeBSD$: two-line .h pattern	2023-08-16 11:54:16 -06:00
Makefile	Remove $FreeBSD$: one-line sh pattern	2023-08-16 11:55:03 -06:00
Makefile.depend	Remove $FreeBSD$: one-line sh pattern	2023-08-16 11:55:03 -06:00