[333] in Zephyr_Bugs
Re: neskaya zephyrd losing
daemon@ATHENA.MIT.EDU (lwvanels@Athena.MIT.EDU)
Fri Jan 17 05:20:01 1992
From: lwvanels@Athena.MIT.EDU
Date: Fri, 17 Jan 92 05:19:50 -0500
To: jfc@Athena.MIT.EDU
Cc: bug-zephyr@Athena.MIT.EDU
In-Reply-To: [332]
Reply-To: lwvanels@mit.edu
>Anyone can subscribe to <login,*,*>, even though the acl disallows this.
There was a problem in the way the class hash table was being searched
for acls; a new zephyrd that fixes this has been installed.
>There are a large number of messages in the zephyr syslog file like:
>
> Jan 16 17:55:00 neskaya zephyrd[3761]: lost client 2.0.9.71/2375
>
>(bad host address) and
>
> Jan 16 17:55:03 neskaya zephyrd[3761]: bad packet receive: Bad packet format
The bogus address was because inet_ntoa was being passed sockaddr_in instead
of sockaddr_in.sin_addr in the call to syslog; I'm not sure of the cause of
the bad packets being sent by the clients, but the new version is logging
more information now to help determine the cause-
>Zephyr locations have been unreliable and unpredictable too.
This is due to a known bug in the old zephyr server code (which is not present
the new server). Unfortunately, the location database corruption will
continue to occur until b11zephyr is running the new server as well.
-Lucien
