home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sun.admin:6211 comp.unix.admin:4953
- Path: sparky!uunet!gatech!wrdis01!wpdis01!iron!hanrahan
- From: hanrahan@iron.hq.aflc.af.mil (Kevin Hanrahan)
- Newsgroups: comp.sys.sun.admin,comp.unix.admin
- Subject: Re: biff not biffing
- Message-ID: <Bu9z6n.3Mt@iron.hq.aflc.af.mil>
- Date: 8 Sep 92 19:51:58 GMT
- References: <1992Aug29.190229.19212@europa.asd.contel.com> <1992Aug29.202158.22016@europa.asd.contel.com> <1992Aug29.211845.21326@ccu.umanitoba.ca> <BtxGD1.1sM@cs.psu.edu>
- Organization: AFSAC
- Lines: 26
-
-
- >>In <1992Aug29.202158.22016@europa.asd.contel.com> pascoe@rocky.gte.com (Dave Pascoe) writes:
- >>
- >>>commented out comsat in /etc/inetd.conf and sent a kill -1 to inetd
- >>>and then uncommented comsat and sent another kill -1.
- >>
- >>>The comsat daemon was out to lunch for some reason. This is a common
- >>>problem on machines which handle a lot of mail, since the comsat
- >>>daemon can tend to get confused at to what state it's in when a SIGHUP
- >>>to inetd comes along.
-
- We have the biff problem at our site. We tried this solution, and it
- worked ... for about 5 minutes, and the problem returned. We have
- tried a couple of other suggestions made here, but none worked either.
-
- We found an interesting corrolation here today: the biff problem
- only is apparent when comsat tries to biff users with login names
- of 8 characters. If the user has less than 8 chars, it works
- just fine.
-
- Could it be that the author of comsat forgot that strings in C
- need to be defined as having one more character than the largest
- size? Nah! Anyone having a similar experience?
-
- --
- Kevin M. Hanrahan hanrahan@iron.hq.aflc.af.mil (513) 427-CETA
- CETA Corporation [137.245.81.8] (513) 257-5760
-