On Fri May  5 12:59:09 2000 Kevin Fitzgerrell wrote...
>
>Stan,
>
>The script does return only the alarms in the current alarm history buffer
>- /usr/hstorian/almhist.  Your previous alarm history buffer (from before
>the AP reboot) should still be available as /usr/hstorian/almhist.bak. If
>you want the ascii listing of that file, you can change the third line in
>the script from
>ALMHIST=/usr/hstorian/almhist
>to
>ALMHIST=/usr/hstorian/almhist.bak
>and it will generate a listing of your previous alarm history buffer.
>
>I know an AP reboot starts a new buffer.  I think stopping and restarting
>the historian does the same thing, but I'm not sure.
>

        I was not complaining, just observing, on the comments. i _might_ if I
        find time comment it, and repost it.

        As for teh alamr history loss on rebooot, I actaully on tied the 2
        together while typing the meaasge. But now it make sense.

        Now onto my soapbox.

        The reason that the AP rebooted this moring is because of a known bug
        in Solaris 2.5.1. This bug is fixed in newer releases, and there is a
        SUN patch for 2.5.1

        I am having a real problem with living with problems that SUN has
        fixed, but Foxboro has not blessed the fix! What are other peoples
        opinion on this?

-- 
Stan Brown     [EMAIL PROTECTED]                                    843-745-3154
Charleston SC.
-- 
Windows 98: n.
        useless extension to a minor patch release for 32-bit extensions and
        a graphical shell for a 16-bit patch to an 8-bit operating system
        originally coded for a 4-bit microprocessor, written by a 2-bit 
        company that can't stand for 1 bit of competition.
-
(c) 2000 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

Reply via email to