dantzspam Posted April 27, 2003 Report Share Posted April 27, 2003 I'm tired of wasting time on why the client turns itself off. Run this from ~/.login or for that matter cron(8) #! /bin/csh set PITOND="/Applications/Utilities/Retrospect Client.app/Contents/Resources/pitond" set retropid=`ps -auxww | grep pitond | grep Retrospect | awk '{print $2}'` if ($retropid) kill $retropid "$PITOND" & If pitond sets a *.pid file, then re-write the above -- I'm out of patience. Link to comment Share on other sites More sharing options...
source Posted September 23, 2003 Report Share Posted September 23, 2003 I have the same issue. Is that a script posted? What was the solution? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.