[DRIVERS-2113] [FLE] Have drivers choose a default PID file and domain socket path Created: 30/Jul/19  Updated: 31/Mar/22

Status: Backlog
Project: Drivers
Component/s: Client Side Encryption
Fix Version/s: None

Type: Spec Change Priority: Major - P3
Reporter: Kevin Albertson Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on MONGOCRYPT-115 Expose a default system dependent PID... Backlog
Related
related to DRIVERS-1861 [FLE] Clarify spawning and connecting... Backlog
Driver Changes: Needed

 Description   

mongocryptd uses a PID file to act as a singleton process. By default it creates the PID file in the current working directory. Instead, we should use a sensible user-specific default path, determined by libmongocrypt in CDRIVER-3260.

Similarly, we should choose a user specific domain socket path.

Also consider having drivers read the PID file. This could detect if a user already has a spawned mongocryptd listening on a different port than what they're attempting to spawn/connect to.



 Comments   
Comment by Kevin Albertson [ 08/Oct/19 ]

That is an old comment. I think given the difficulties that have been encountered of auto spawning during the beta, we want to do something to improve mongocryptd spawning. I think it's TBD how much we want to improve mongocryptd spawning for GA, but this would be one possible improvement.

Generated at Thu Feb 08 08:24:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.