mirror of
git://jb55.com/damus
synced 2024-09-30 08:50:42 +00:00
dcafcd9184
mdb_env_setup_locks: using semnames 'group.com.damus/MDBrwDDi_FHxD' (29), 'group.com.damus/MDBwwDDi_FHxD' (29) From old Apple docs: > IPC and POSIX Semaphores and Shared Memory > > Normally, sandboxed apps cannot use Mach IPC, POSIX semaphores and > shared memory, or UNIX domain sockets (usefully). However, by specifying > an entitlement that requests membership in an application group, an app > can use these technologies to communicate with other members of that > application group. > > Note: System V semaphores are not supported in sandboxed apps. > > UNIX domain sockets are straightforward; they work just like any other > file. > > Any semaphore or Mach port that you wish to access within a sandboxed > app must be named according to a special convention: > > POSIX semaphores and shared memory names must begin with the application > group identifier, followed by a slash (/), followed by a name of your > choosing. > > Mach port names must begin with the application group identifier, > followed by a period (.), followed by a name of your choosing. > > For example, if your application group’s name is > Z123456789.com.example.app-group, you might create two semaphores named > Z123456789.myappgroup/rdyllwflg and Z123456789.myappgroup/bluwhtflg. You > might create a Mach port named > Z123456789.com.example.app-group.Port_of_Kobe. > > Note: The maximum length of a POSIX semaphore name is only 31 bytes, so > if you need to use POSIX semaphores, you should keep your app group > names short. Link: https://github.com/damus-io/damus/issues/2323#issuecomment-2323305949 Signed-off-by: William Casarin <jb55@jb55.com> |
||
|---|---|---|
| .. | ||
| project.xcworkspace | ||
| xcshareddata/xcschemes | ||
| project.pbxproj | ||