[SERVER-10263] Failure to use absolute path for --pidfilepath will result in no pidfile being created Created: 19/Jul/13  Updated: 10/Dec/14  Resolved: 19/Jul/13

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: 2.4.5
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Joe Drumgoole (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux/Unix/OSX


Issue Links:
Duplicate
duplicates SERVER-6655 pid file does not get created when pa... Closed
Related
is related to SERVER-10034 Invalid --pidfilepath is silently ign... Closed
Operating System: ALL
Participants:

 Description   

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.


Generated at Thu Feb 08 03:22:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.