> Here is the patch.  It works under both Solaris and Linux.

Thanks! I put that into revision #2207.

I could not reproduce your problem. I can only fix it if I can reproduce it, so let's agree on a common test base. May I ask you to do the following:

• Download the most recent elog version from bitbucket and compile it
• Create two new logbooks "demo1" and "demo2" with minimal configuration, but using yor global password file which differs from the group ones
• Send me step-by-step instructions how to trigger the problem, including your elogd.cfg file and your password files (of course with fake accounts)

If I can reproduce the crash, I can fix it.

> elogd is crashing with a segv when I try to create a new logbook by clicking the "Create new logbook" button
> with an existing logbook selected in the dropdown list as a template. I've attached my config file for
> reference. As a specific example, I'm logged in as the admin user, viewing logbook "1248", which has no entries,
> and I click "Config" -> "Change config file" -> "Create new logbook", Select "1248" from dropdown list, enter
> "1250" for the new logbook name, and click "Create new logbook".
> 
> The server crashes, and my web browser has the following as the (incorrect) URL it's trying to load:
> (Incorrect because the "/ATLAS" shouldn't be there.)
> 
> https://localhost:8080/ATLAS/1250/?cmd=Config
> 
> Nevertheless, the config file and logbook directory are properly modified for the new logbook, and on restarting
> the server, everything is fine.
> 
> Oh, just noticed that if I manually enter the URL:
> 
> https://localhost:8080/ATLAS/1250/
> 
> or actually, any text in place of the "1250", it also crashes the elogd process. So, perhaps there are two bugs?
> 
> (1) Incorrect URL being given to the web client after logbook creation
> (2) Requesting any incorrect URL of this form crashes elogd

This problems have been fixed in SVN revision 2135.

It's hard to tell the problem from what you report. Have you tried the latest
release http://midas.psi.ch/elog/download/windows/elog258-6.exe ? There were
some problems with the password file in 2.5.8 versions prior to patch level 6.

> It's hard to tell the problem from what you report. Have you tried the latest
> release http://midas.psi.ch/elog/download/windows/elog258-6.exe ? There were
> some problems with the password file in 2.5.8 versions prior to patch level 6.

Yes, I am up to date with the latest version (2.5.8-6).

What other information can I provide that might assist in diagnosing this?

> What other information can I provide that might assist in diagnosing this?

Please send me your elogd.cfg configuration file.

> > What other information can I provide that might assist in diagnosing this?
> 
> Please send me your elogd.cfg configuration file.

Stefan - I am having the exact same problem as outlined here. I sent you an
email with a somewhat complicated config file. Attached to this message is a
much simpler one. 

With this file, if you remove the B5 server (remove it from top group a2, and
remove the [b5] entry) the crash does not happen. If the B5 server (or any
additional server) is in the file, then the problem occurs.

For me, there are 3 places where the crash happens:
- on logout
- when an invalid username/password is used to login
- when you login to A1, then try to go to A2

This is happening on elog v2.5.9-1 (built May 2, 2005, 12:17:18 revision 1.642)

I have tried on windows 2000 and 2003 servers, and it seems to happen on both of
them.

Matt