Xref: utzoo news.software.b:1764 comp.sys.pyramid:264 Path: utzoo!attcan!uunet!peregrine!elroy!ames!ucsd!orion.cf.uci.edu!paris.ics.uci.edu!nagel From: nagel@paris.ics.uci.edu (Mark Nagel) Newsgroups: news.software.b,comp.sys.pyramid Subject: Re: Problem with disappearing history file Message-ID: <945@paris.ics.uci.edu> Date: 20 Nov 88 00:37:04 GMT References: <5849@polyslo.CalPoly.EDU> <264@ispi.UUCP> Sender: news@paris.ics.uci.edu Reply-To: nagel@paris.ics.uci.edu (Mark Nagel) Followup-To: news.software.b Distribution: na Organization: University of California, Irvine - Dept of ICS Lines: 27 In-reply-to: jbayer@ispi.UUCP (Jonathan Bayer) In article <264@ispi.UUCP>, jbayer@ispi (Jonathan Bayer) writes: |In article <5849@polyslo.CalPoly.EDU>, steve@polyslo.CalPoly.EDU (Steve DeJarnett) writes: |> |> Has anyone had any problems with a history file in 2.11.14 |> that decides to disappear occasionally??? We've had this problem |> occur enough times that I am sure it's not related to running out |> of disk space or other hardware-related problems. When this |> happens, I get a message (as news) saying something to the effect |> of: |> |> "There was a problem with the history file. It has been fixed." | |We had a problem like this a while ago. It turned out that we were |running 2 expires at the same time, which got both of them very |confused and made the history file disappear occasionally. As did we, but we lost our *active* file. It turns out to be some kind of bug in the SunOS 4.0 cron that caused the nightly script to execute twice simultaneously. I worked around it by adding a "script lock" to the nightly script. I.e., I just had the script check for the existence of a lock file in /tmp and if present, exit. If not, create it and go on. Haven't had any problems since. Mark D. Nagel UC Irvine - Dept of Info and Comp Sci | The probability of someone nagel@ics.uci.edu (ARPA) | watching you is proportional to {sdcsvax|ucbvax}!ucivax!nagel (UUCP) | the stupidity of your action.