Clark Kent should write its lock file after it forks

[Jason Stephenson]

Eg Version: 2.7.1 (affects all prior versions)
OpenSRF: 2.4 (N/A)
Postgresql: (N/A)
O/S: (N/A)

The reporter, clark-kent.pl, writes it's process ID (pid) to the lock file before it forks into the background. This means that the pid in the lock file cannot be used to stop the running reporter process. At best, the pid will reference no running process. At worst, you will kill some other unknown process on a busy system if all pids have been cycled since Clark started or if the system uses a randomized process for assigning process IDs.

A branch to fix this will be forthcoming....

[Jason Stephenson (jstephenson)]

Branch in user/dyrcona/lp1435966_reporter_pid_fix in the working repo:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dyrcona/lp1435966_reporter_pid_fix

[Galen Charlton (gmc)]

Tested and looks good. Pushed to master, rel_2_8, rel_2_7, and rel_2_6. Thanks, Jason!