diff options
| -rw-r--r-- | Base/usr/share/man/man7/Audio-subsystem.md | 7 | ||||
| -rw-r--r-- | Documentation/Browser/ProcessArchitecture.md | 2 |
2 files changed, 4 insertions, 5 deletions
diff --git a/Base/usr/share/man/man7/Audio-subsystem.md b/Base/usr/share/man/man7/Audio-subsystem.md index 1ef9174919..ff7aa46588 100644 --- a/Base/usr/share/man/man7/Audio-subsystem.md +++ b/Base/usr/share/man/man7/Audio-subsystem.md @@ -1,6 +1,6 @@ ## Name -Overview of the SerenityOS audio subsystem, including a brief description of [`/dev/audio`](help://man/4/audio), the AudioServer and their interfaces. +Overview of the SerenityOS audio subsystem, including a brief description of [`/dev/audio`](help://man/4/audio), the AudioServer and their interfaces. ## Description @@ -18,9 +18,8 @@ AudioServer is responsible for handling userland audio clients and talking to th application should ever need to write to a device in `/dev/audio` directly, except for special cases in which AudioServer is not present. -As with all system servers, AudioServer provides an IPC interface on `/tmp/user/%uid/portal/audio`, with `%uid` being -the uid -of the current user. For specifics on how to talk to AudioServer, the IPC interface specifications are the best source +As with all system servers, AudioServer provides an IPC interface on `/tmp/session/%sid/portal/audio`, with `%sid` being +the current login session id. For specifics on how to talk to AudioServer, the IPC interface specifications are the best source of information. For controlling mixer functionality, clients have the ability to obtain and change their own volume, or the main volume and mute state. diff --git a/Documentation/Browser/ProcessArchitecture.md b/Documentation/Browser/ProcessArchitecture.md index ea065f8304..6a4e0a13fc 100644 --- a/Documentation/Browser/ProcessArchitecture.md +++ b/Documentation/Browser/ProcessArchitecture.md @@ -31,7 +31,7 @@ This process can decode images (PNG, JPEG, BMP, ICO, PBM, etc.) into bitmaps. Ea ### How processes are spawned To get a fresh **WebContent** process, anyone with the suitable file system permissions can spawn one by connecting to -the socket at `/tmp/user/%uid/portal/webcontent`, with `%uid` being the uid of the current user. This socket is managed +the socket at `/tmp/user/%sid/portal/webcontent`, with `%sid` being the current login session id. This socket is managed by ** SystemServer** and will spawn a new instance of **WebContent** for every connection. |