Failure to use absolute path for --pidfilepath will result in no pidfile being created

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Minor - P4
    • None
    • Affects Version/s: 2.4.5
    • Component/s: Internal Code
    • None
    • Environment:
      Linux/Unix/OSX
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Unassigned
              Reporter:
              Joe Drumgoole (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: