According to [EMAIL PROTECTED]: > last night my indexing run got crushed down with the following message... > > [htdig] ./htdig-3.2/bin/rundig: line 36: 3903 Killed > > Any idea how to get this problem solved....???
"Killed" usually means terminated with SIGTERM, or possibly even SIGKILL. This doesn't usually happen on its own, but by explicit user (or administrator) action to kill the process. Maybe the htdig process was dragging the system down, so someone had to kill it. > htdig_version: 3.1.0b4 I assume you actually mean 3.2.0b4. If you're not running a recent snapshot of 3.2.0b4, I suggest you obtain the latest one. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This sf.net email is sponsored by: Are you worried about your web server security? Click here for a FREE Thawte Apache SSL Guide and answer your Apache SSL security needs: http://www.gothawte.com/rd523.html _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
