| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
// legacy simngle-process host, the server is run as the login user.single
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
// legacy simngle-process host, the server is run as the login user.Yuwei Huangsingle
Oops! Done :)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
9 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: remoting/host/chromoting_host_services_server.cc
Insertions: 1, Deletions: 1.
@@ -57,7 +57,7 @@
: ChromotingHostServicesServer(
#if BUILDFLAG(IS_LINUX)
// For the multi-process host, the server is run as root; for the
- // legacy simngle-process host, the server is run as the login user.
+ // legacy single-process host, the server is run as the login user.
(getuid() == 0) ? GetChromotingHostServicesServerName()
: GetLegacyChromotingHostServicesServerName(),
#else
```
remoting Linux multi-process: Fix ChromotingHostServices
The single-process host uses `chromoting.$USER.host_services_mojo_ipc`
as the socket name due to multi-user support, but for the multi-process
host, the socket is created by the daemon process, which is run as
root, so this doesn't work. This CL fixes this by making the IPC server
in the daemon process use `chromoting.host_services_mojo_ipc` as the IPC
name. Since the client doesn't know if the host is single- or
multi-process, it is updated to try both socket names and see which one
works.
This is not done yet. In the next CL, I'll hook
DaemonProcessLinux::BindChromotingHostServices into
DesktopSessionFactoryLinux so that a request can be routed to the
correct user/desktop session.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |