[ic] access.gdbm corruption?

[Mike Heins]

Quoting Bob Keyes (bkeyes@Consilium-III.Com):
> 
> On Fri, 3 Jan 2003, Jeff Dafoe wrote:
> 
> >
> >     I should clarify my statement by saying that "multiple users" means
> > "multiple sessions".  A single physical person could generate multiple
> > sessions, I do this by opening both IE and netscape.
> >
> 
> 
> Thanks. I had thought of that and checked, but just realized I had missed
> one terminal window open on the server itself. Oops!
> 
> Though IC should really have a way to not die when this happens. Feature
> Request: When an account is logged in more than once, the second user
> trying to log in should get a message to the likes of:
> 
> "This user is alredy logged in from {hostname}, idle since {last activity
> time). Close this old session? (Yes/No)"
> 
> I'd try to code this myself, if I knew more about how the interchange
> internals work.
> 

It really has nothing to do with more than one user on the same account.
It is just GDBM timing out for write after a long access holds off a 
user for more than a certain period of time.

I suppose I could put in a Limit parameter that makes that configurable.

-- 
Mike Heins
Perusion -- Expert Interchange Consulting    http://www.perusion.com/
phone +1.513.523.7621      <mike@perusion.com>

Experience is what allows you to recognize a mistake the second
time you make it. -- unknown