To edit pages or tickets please login with username/password: aaf/aaf

Ticket #195 (closed defect: fixed)

Opened 8 months ago

Last modified 7 months ago

[PATCH] write_pid_file should not overwrite an existing pid file

Reported by: aaf Assigned to: jk
Priority: major Milestone:
Component: 0plugin Version:
Keywords: Cc:

Description

If you call ferret_server start when the server is already running it removes the old pid file. Once this happens ferret_server is no longer able to stop the daemon.

The pid file is written before the server is fully up, and write_pid_file does not check to see if a pid file already exists. So when a server fails to start (address already in use) a failing server start overwrites the pid file with its (new) pid, and then deletes it as it exits.

This patch simply adds a descriptive error message when a pid file is attempting to be overwritten.

Eli Miller

Attachments

acts_as_ferret-raise_exception_on_existing_pid_file.diff (0.6 kB) - added by aaf on 01/16/08 20:33:09.

Change History

01/16/08 20:33:09 changed by aaf

  • attachment acts_as_ferret-raise_exception_on_existing_pid_file.diff added.

02/02/08 12:09:19 changed by jk

  • status changed from new to closed.
  • resolution set to fixed.

fixed in trunk

To edit pages or tickets please login with username/password: aaf/aaf