[Sean Conner]

I have found that for whatever reason, Phlink will sometimes choke or unexpectedly quite. I have it running on Mac OS X Server 10.3.4 (headless) and don't continually moniter it, however I want to know that it is ON to receive calls while I'm away. To solve this problem I have altered my crontab to automatically quite and restart Phlink (in addition to clearing out any Temp files) every three hours using the following sh script:

-------
#! /bin/sh

killall Ovolab\ Phlink
rm -drf /Library/Application\ Support/Phlink\ Items/Temp*
open /Applications/Ovolab\ Phlink.app
-------

However, I've found that with Phlink 1.4.2, this script completely hangs my machine. If I try to kill Phlink with the kill command from a terminal using the process ID, I get the same result. Any ideas what has changed with Phlink that may cause this? I have also tried an Applescript and this appears to work for a while, but it will eventually cause a hang.

-----
tell application "Ovolab Phlink"
activate
quit
end tell

tell application "Finder"
activate
open "Applications:Ovolab Phlink"
end tell
------

I end up with a connection error or error code -600. The only fix I can come up with is to revert back to Phlink 1.4.1.