From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ip15.shellworld.net ([64.49.204.174] helo=server2.shellworld.net ident=root) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1HT0sf-0003Nb-00 for ; Sun, 18 Mar 2007 15:17:25 -0400 Received: from ip15.shellworld.net (jdashiel@ip15.shellworld.net [64.49.204.174]) by server2.shellworld.net (8.13.1/8.12.8) with ESMTP id l2IJHO85046092 for ; Sun, 18 Mar 2007 19:17:24 GMT (envelope-from jdashiel@shellworld.net) Date: Sun, 18 Mar 2007 15:17:24 -0400 (EDT) From: Jude DaShiell To: speakup@braille.uwo.ca Subject: re: podracer Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.9 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2007 19:17:26 -0000 It could be for whatever reason podracer isn't actually running more than once a day no matter what is in a user's crontab file. The reason I write this is that on more than one occassion I've had instances where I ran podracer on the 4 hour times crontab ought to have run it. Now if podracer had been running, you would expect the prompt to come back very fast since podracer would prevent itself from running more than one instance of itself in the same account at the same time. Those pauses until the prompt reappeared lasted into the minutes. Now It could be I should be using opendomain.org's primary and secondary domains rather than the ones verizon provided me but I have to test this out.