Facebook

Fill out this form to subscribe to news, tips and information about updates.

Read more
Search known errors
From date:
To date:

Follow us
Facebook    Twitter    LinkedIn

G&R » Support » Known Errors  

Known Errors

These are the known errors in our products, logged as reported with versions and platforms affected as well as corrections and work-arounds.

This list is largely historical, since it records all problems that have been reported throughout G&R history. Only the most recently reported problems still exist, unless you are using a very old copy of the product, in which case you should update the product to the most recent version.


E0429: Ggate, 'kill all' unpredictable in some configurations.

Product: Host Links (Ggate) and Glink
Platform: Any
Status: Fix in Host Links 5.2.0 and Glink 6.1
Last updated: 1998-07-31 14:34:20

When a single Glink users' 'kill all' request was received by
Ggate, the IP address was used to identify sessions orginating
from that user and all active session having the same IP address
as the one in the 'kill all' request were terminated.

This works fine in most configurations. However - in some
configurations, some (all) clients could have the same IP
address (e.g. some firewall types, WinFrame configurations etc.),
and this could lead to a situation where a 'kill all' request
from a single user could terminate several (in the worst case
all) other user sessions.

Also - in some configurations an IP address would be dynamically
assigned on a session basis so that 2 different sessions from the
same workstation would appear as 2 different users for Ggate and
hence a 'kill all' would not work.

In order to be able to uniquely identify a Glink workstation we
have introduced a new identifier called a GUID which is passed
on to Ggate by all Glinks on the same platform in the initial
Ggate dialog, and used by Glink in the 'kill all' packet. This
GUID is used by Ggate to find active sessions originating from
the same user/workstation as the 'kill all'.

This approach solves the above mentioned problems with 'kill
all' but requires that Glink is updated to 6.1 for all clients.

To protect Ggate configurations where Glink for some reason
cannot be updated, the 'kill all' logic in Ggate has been
limited to not perform the 'kill all' request if more than 10
sessions are found to be candidates for the request.

This kill limit can be adjusted with a new '-kl n' Ggate
parameter. Setting 'n' to 0, will effectivly disable the 'kill
all' logic completely.

(c) Copyright 1982-2017 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

URL: http://www.gar.no/support/errors
 
PARTNERS