Return to BSD News archive
Xref: sserve comp.unix.bsd:12676 comp.unix.wizards:30920 comp.sys.sun.apps:4882 comp.sys.sun.misc:9713 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!news.wonderworks.com!u-sure-kin-mambo From: kyle@crystal.WonderWorks.com (Kyle Jones) Newsgroups: comp.unix.bsd,comp.unix.wizards,comp.sys.sun.apps,comp.sys.sun.misc Subject: Re: checkpointing software for UNIX or SunOS Date: 25 Sep 1993 14:41:50 -0400 Organization: Wonderworks Inc. Lines: 14 Message-ID: <2823de$5l4@crystal.WonderWorks.com> References: <TMB.93Sep23012442@arolla.idiap.ch> <VIXIE.93Sep22202934@gw.home.vix.com> <27scjl$qjc@agate.berkeley.edu> NNTP-Posting-Host: crystal.wonderworks.com eric@CS.Berkeley.EDU writes: > It's worth pointing out that this is VERY hard to get right > and even harder to do portably. For example, there can be > system routines that have resources open that you know nothing > about. I've taking the freeze file out of sendmail entirely > -- it was more trouble than it was worth. Absolutely agree. The surprises are unimaginable. The only way I found to do it portably was to have the program write its internal data out as C structures and then recompile itself. I did this for a LISP system a few years ago, and the only portability problem I've had to date is that the large C data files produced made pcc gag.