Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!apple!usc!csun!fedeva!premise!mirror!roskuski
From: roskuski@mirror.UUCP (Barry Roskuski)
Newsgroups: comp.sys.pyramid
Subject: Re: comsat and biff
Summary: The alarm doesn't alarm
Message-ID: <28100@mirror.UUCP>
Date: 26 Jun 89 14:34:20 GMT
References: <17033@bellcore.bellcore.com>
Reply-To: roskuski@prism.TMC.COM (Barry Roskuski)
Followup-To: comp.sys.pyramid
Organization: Mirror Systems, Cambridge Mass.
Lines: 20

In article <17033@bellcore.bellcore.com> tr@ctt.bellcore.com (tom reingold) writes:
>On one of our two Pyramids, users get biff messages for other users.  I
>think this is comsat's fault, but I can't check because Pyramid's

    We have had 2 problems at our site. The one you describe, and 
    people not getting biff'ed at all when they should be. Apparently,
    the SIGALRM that comsat uses to keep it's list of logged on users
    up to date stops going off for an unexplained reason, and the configuration
    gets 'frozen' (In our case, the *other users* that the people get biff'ed
    for are people who were logged on to the terminal at some point in
    the past). A "kill -ALRM pid" (where pid is the pid of comsat) puts
    it back in synch.

                                    Hope this helps.
------------------------------------------------------------------------------
Barry J. Roskuski                   Mirror Systems
                                    2067 Massachusetts Ave.
                                    Cambridge, MA 01240
roskuski@mirror.TMC.COM
{mit-eddie, pyramid, wjh12, xait, datacube}!mirror!roskuski