Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tdatirv!sarima
From: sarima@tdatirv.UUCP (Stanley Friesen)
Newsgroups: comp.windows.x
Subject: Re:  resource ID allocation
Message-ID: <158@tdatirv.UUCP>
Date: 4 Mar 91 17:21:44 GMT
References: <9102140823.AA17984@lightning.McRCIM.McGill.EDU> <5366@acorn.co.uk>
Reply-To: sarima@tdatirv.UUCP (Stanley Friesen)
Organization: Teradata Corp., Irvine
Lines: 21

In article <5366@acorn.co.uk> john@acorn.co.uk (John Bowler) writes:
<In article <9102140823.AA17984@lightning.McRCIM.McGill.EDU> mouse@lightning.mcrcim.mcgill.EDU writes:
<>> If not, clients which manage a lot of resources for a long time may
<>> run out of valid ID's.

<>This seems like a silly thing to worry about. ...

<Over christmas 1989 I ran Xvstress from the X Test Suite on (against :-))
<one of our servers.  When I came back (after about two weeks) the
<XVSpixmap test had failed with a BADIDChoice error. ...

I have just run into another, more serious example of this problem.
Twice now my xlock has bombed, apparently because it ran out of ID's.
This is a potential security problem, since my workstation was sitting
there, logged in, all weekend.  [Sigh, I normally do log out, but I wanted
to save an error message to show someone today].

xlock, at least, needs to be fixed to run indefinately.
-- 
---------------
uunet!tdatirv!sarima				(Stanley Friesen)