ken@gvax.cs.cornell.edu (Ken Birman) (02/18/91)
With the help of Jay Nietling (jay@cs.unlv.edu), we've tracked down the cause of the infinite loop in bin/protos that has me puzzled. There is a variable in ISIS that represents the time since the system was booted on this node, in milliseconds, and it overflows after ISIS is up on your machine for 24 days. When this happens, bin/protos goes into an infinite loop in a protocol called the "associative store", which uses a timer mechanism that begins to malfunction. I'll post a fix shortly. Thanks, Jay! I probably wouldn't have caught this without your help, since we tend to switch versions of ISIS here at Cornell more frequently than every 24 days, and so we do a complete system shutdown/restart before the bug kicks in... Ken