-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Security 2020-02-24, Security 2020-03-09, Security 2020-03-23, Security 2020-04-06, Security 2020-04-20, Security 2020-05-04, Security 2020-05-18, Security 2020-06-01, Security 2020-06-15, Security 2020-06-29
mongocryptd launched with the only argument of --idleShutdownTimeoutSecs=60 creates a socket file in /tmp and a pid file in the current directory:
2020-01-30T18:21:16.802-0500 I CONTROL [initandlisten] Using lock file: /home/w/apps/ruby-driver/mongocryptd.pid 2020-01-30T18:21:16.818-0500 I NETWORK [initandlisten] Listening on /tmp/mongocryptd.sock
Since both files are associated with the same process, they should be placed in the same principal location (either global to the system or local to the application launching mongocryptd/current directory).
As I understand it, mongocryptd is intended to be system-global/shared; if this is correct, I expect the pid file to be placed in a system-global/shared location as well (e.g. /var/run on systems obeying FHS, see http://www.pathname.com/fhs/2.2/fhs-5.13.html).
Tested on 4.2 server built from source recently.
- related to
-
-
- Closed
-