RE: [NeoStats-Devel] GDBM problem - WAS Re: [NeoStats-Devel] NeoStats 3.0 alpha 2 pre release notice

> > > The debug log shows an error:
> > > 
> > > 09/03/2005[01:09:09] DEBUG4 SecureServ - DBMOpenTable 
> > > 09/03/2005[01:09:09] DEBUG1 SecureServ - gdbm_open fail:
> > > Can't be writer
> > 
> > Can we bail on errors like this? (as in Exit NeoStats....) 
> > I'm sure that there will be many users that will do something 
> > funky, and we will get errors like this in the log files, and 
> > users being users, they will not check log files, and the log 
> > support requests because their settings or data don't get saved. 
> 
> I do want to bail eventually, but at present, UNLOAD module 
> followed by LOAD
> module would close down NeoStats every time for DNB but I 
> have not found a
> way around it yet. 
> 

Looking at the code, it seems that the flock call fails... You could try
adding GDBM_NOLOCK to the flags when we open the database.... Which, if we
specify that GDBM cannot be used by multiple processes, we should avoid this
problem...