-
Type: Bug
-
Resolution: Duplicate
-
Priority: Minor - P4
-
None
-
Affects Version/s: 2.4.5
-
Component/s: Internal Code
-
None
-
Environment:Linux/Unix/OSX
-
ALL
The --pidfilepath asks for an absolute path as an argument. This is required because the server does a chdir() to root before we write the pidfile and that write will fail if you just specify a filename (e.g. -pidfilepath proc.pid).
This is inconsistent with --logpath which does accept a non-absolute path.
The server should either report an error for a non-absolute path or prepend the cwd() to the pidfilepath argument for non absolute arguments.
This happens when the --fork argument is used.
- duplicates
-
SERVER-6655 pid file does not get created when passing a relative path for --pidfilepath
- Closed
- is related to
-
SERVER-10034 Invalid --pidfilepath is silently ignored
- Closed