From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264942AbUD2Tup (ORCPT ); Thu, 29 Apr 2004 15:50:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264944AbUD2Tup (ORCPT ); Thu, 29 Apr 2004 15:50:45 -0400 Received: from main.gmane.org ([80.91.224.249]:41179 "EHLO main.gmane.org") by vger.kernel.org with ESMTP id S264942AbUD2Tun (ORCPT ); Thu, 29 Apr 2004 15:50:43 -0400 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: "Neal D. Becker" Subject: Re: State of linux checkpointing? Date: Thu, 29 Apr 2004 15:50:38 -0400 Message-ID: References: <409012A4.9000502@pobox.com> <40912DD2.90900@lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 139.85.94.36 User-Agent: KNode/0.7.7 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Tim Connors wrote: > Thomas Davis said on Thu, 29 Apr 2004 09:31:14 -0700: >> Neal Becker wrote: >> > >> > I want checkpointing for: >> > >> > 1) Protect against job interruption due to system crash, operator >> > error, power loss, whatever >> > >> > 2) Job mygration. Even manual job mygration would be nice. >> >> Two possible solutions: >> >> 1) http://ftg.lbl.gov/checkpoint > > Oooh. Shiny. > Looks interesting. Kernel-2.4 only AFAICT.