> Noee. Here it works immediately.
> 
> Can you try with a fresh server from the distribution, with the example 
> elogd.cfg, to see if there is any difference?
> 
> The killing is handled in the funciton ctrlc_handler(), which sets _abort = 
> TRUE. This  is checked in line 16195, just after the select(), and the main 
> loop is exited. The select finishes after one second, although I believe 
> that the kill signal also terminates the select prematurely. The kill 
> command and a Ctrl-C keystroke should work the same way, they both generate 
> a SIGTERM or SIGINT signal.

elogd does not exit if there is an 'unprocessed' HUP.  So when you do 

kill -HUP <pid>
kill <pid> 

elogd will only exit after it was accessed.

> elogd does not exit if there is an 'unprocessed' HUP.  So when you do 
> 
> kill -HUP <pid>
> kill <pid> 
> 
> elogd will only exit after it was accessed.

Can you please tell me how to reproduce this problem?

Even if I do a

kill -HUP <pid>; kill <pid>

it works immediately when I start elogd manually in interactive mode (not as daemon).

> > elogd does not exit if there is an 'unprocessed' HUP.  So when you do 
> > 
> > kill -HUP <pid>
> > kill <pid> 
> > 
> > elogd will only exit after it was accessed.
> 
> Can you please tell me how to reproduce this problem?
> 
> Even if I do a
> 
> kill -HUP <pid>; kill <pid>
> 
> it works immediately when I start elogd manually in interactive mode (not as daemon).

Even though I can't test this right now, I assume you have to wait a little
so that elogd jumps out of the 'select()' statement between the kill
commands.  Try: 

kill -HUP <pid>; sleep 2; kill <pid>

(I think the 'select()' timeout was 1 second.?)

> kill -HUP <pid>; sleep 2; kill <pid>

Thanks, I could reproduce the problem. It had to do that a SIGHUP aborts the select()
command, which some listen socket marked, so that elogd goes into an accept() call, waiting
there indefinitely (or until a new browser request arrives). I fixed that. New version
under CVS.

I was upgrading to the latest version and I wrote over my cfg file. I 
still have my database files. Is there a way to put the cfg file back 
together using the database files as a guide.  It did not seem to want to 
upgrade until I did this and I forgot to copy and then paste the cfg files 
back.  The latest version is now running. Before I did this I was still 
getting the old version number at the bottom of the main screen.  Also I 
have an RSS reader that can do user name and password, is this possible 
with Elog if the RSS reader has the ability?

Thanks

I guess this qualifies as two questions.

David Egolf

> I was upgrading to the latest version and I wrote over my cfg file. I 
> still have my database files. Is there a way to put the cfg file back 
> together using the database files as a guide.  It did not seem to want to 
> upgrade until I did this and I forgot to copy and then paste the cfg files 
> back.  The latest version is now running. Before I did this I was still 
> getting the old version number at the bottom of the main screen.  Also I 
> have an RSS reader that can do user name and password, is this possible 
> with Elog if the RSS reader has the ability?

I put an extra dialog box into the installer to prevent overwriting the
original config file, but unfortunately I cannot prevent people from shooting
themselves into the foot (;-)

The database files contain at least the attributes. Just open any file with a
text editor. But the other settings, like "preset <attribute>" etc. are lost.

Concerning teh RSS authentication, I willing to implement this if you tell me
which reader you are using, so that I can test it. You could also try yourself,
maybe it works without modification. What you would need is public read access
via "Guest menu commands" option plus a "Read password". The read password
prevents again the public read access, but the RSS reader can maybe submit it.
What the RSS reader certainly cannot do is to fill out the "Login" screen of
elog, so you need the "Guest menu commands" for sure.

- Stefan

> > I was upgrading to the latest version and I wrote over my cfg file. I 
> > still have my database files. Is there a way to put the cfg file back 
> > together using the database files as a guide.  It did not seem to want to 
> > upgrade until I did this and I forgot to copy and then paste the cfg files 
> > back.  The latest version is now running. Before I did this I was still 
> > getting the old version number at the bottom of the main screen.  Also I 
> > have an RSS reader that can do user name and password, is this possible 
> > with Elog if the RSS reader has the ability?
> 
> I put an extra dialog box into the installer to prevent overwriting the
> original config file, but unfortunately I cannot prevent people from shooting
> themselves into the foot (;-)
> 
> The database files contain at least the attributes. Just open any file with a
> text editor. But the other settings, like "preset <attribute>" etc. are lost.
> 
> Concerning teh RSS authentication, I willing to implement this if you tell me
> which reader you are using, so that I can test it. You could also try yourself,
> maybe it works without modification. What you would need is public read access
> via "Guest menu commands" option plus a "Read password". The read password
> prevents again the public read access, but the RSS reader can maybe submit it.
> What the RSS reader certainly cannot do is to fill out the "Login" screen of
> elog, so you need the "Guest menu commands" for sure.
> 
> - Stefan

Hello,

Thank you so much for working with me on this.  The RSS reader I have been trying 
is at http://www.rssreader.com   and is version 1.0.88.0  It is a free RSS reader 
and seems to work very well.  It has a username and password system, but I am not 
sure what and how it will support with ELog. I have been successful in reading an 
open logbook with no passwords.  

Thanks again,

David Egolf

> Thank you so much for working with me on this.  The RSS reader I have been trying 
> is at http://www.rssreader.com   and is version 1.0.88.0  It is a free RSS reader 
> and seems to work very well.  It has a username and password system, but I am not 
> sure what and how it will support with ELog. I have been successful in reading an 
> open logbook with no passwords.  

rssreader supports HTTP authentication. So what you have to do is to define a "read
password". Open a dos box, navigate to your elog directory, and enter

elogd -l <logbook> -r <password>

replace <logbook> with your real logbook name and <password> with any password. This
command modifies elogd.cfg and puts your password there in encrypted form.

Next, tell rssreader to use authentication and enter there your password
(authetication name does not matter). See the attachment. Rssreader will then be able
to connect properly to your logbook.