> [...] It appears that npp=0 crashes elogd [...]

Here's a patch: search for "npp" in src/elogd.c and add the following line:
  if (n_page<=0) n_page = 20;

Here's the diff output for version 2.9.0-2414
*** 20092,20096 ****
     if (isparam("npp"))
        n_page = atoi(getparam("npp"));
+    if (n_page<=0) n_page = 20;

     if (page_mid) {

Some user wanted to modify the URL by hand and succeeded to crash the elogd process with npp=now
It appears that npp=0 crashes elogd with the following error message:

Program received signal SIGFPE, Arithmetic exception.
0x0808eba2 in show_elog_list (lbs=0xab3c770, past_n=0, last_n=0, page_n=1,
    default_page=1, info=0x0) at src/elogd.c:20214
20214            sprintf(str + strlen(str), loc("Page %d of %d"), page_n, (n_msg - 1) / n_page + 1);

I guess this bug is not OS dependent: you can crash every logbook that you can search ;-)

Dear ELOG users,

the ELOG discussion forum at PSI contains in meantime many old accounts with non-functional email addresses. Since this causes some overhead, it has been decided to clean up the current account database. In order to keep your account alive, please log in at the above forum before Friday, Sept. 30th, 2011.  If you fail to log in until that date, your account will be automatically deleted. Note that it will be always possible to re-create your account afterwards by simply clicking on "Register as new user", but before that you won't get automatic email notifications any more once your account has be deleted.

Sorry for the inconvenience, but the database contains currently too many wrong email addresses causing some flooding of our mail systems.

Best regards,

     Stefan Ritt

 Fantastic! That worked great. Thanks so much for the help guys!!

Terry

Best is if you edit elgod.cfg or the user configuration from inside the web browser (Click on 'config' on the elog page), then you don't have to restart elogd. If you do have to restart it, go to My Computer/Manage/Services, select elogd, then stop and start the service.

- Stefan

If you start over, you can just copy the xxyyzza.log files into the new logbook directory and it should be fine. You can also change the config file in your current logbook without starting over. 

> > I wondered if there had been some flag for the config file whereby the original file for attachment was
> > processed by ImageMagick, but not stored, only the .png file(s) stored - or rather, some other way that achieved
> > the same end. as there is no such flag at present.
> > 
> > For now, anyway, I can attach the documents/pics I want, then go in and delete the 'originals' as saved in the
> > logbook, leaving just the .png files. But maybe something for the wishlist?
> 
> At least I now understood your problem :-)
> 
> You can have a script in your hidden logbook, that processes your attachments with "execute new", create thumbnails
> of them (using ImageMagicks "convert") and submit those thumbnails as one additional entry to your public logbook.
> 
> But then you would get thumbnails of all attachments of the hidden logbook in the public one, maybe you don't want
> that either? If you want them all, this method is more automated. If you just want some, do it as you suggested it.
> 
> In my opinion this is a rather exotic feature request :-)
> I wonder if there is a second person in the world who could use it?

Hi Andreas,

True, as a feature explained here, it may not be the most frequently used ;-)

And you are right, I would not want *all* attachements in the hidden directory to appear in the public.  But I've got
quite used to playing around in the logbook subdirectories now.

In my case, the ever-expanding use I make of ELOG - and the fact that I use it with the logbook directory stored on a
memory stick (to move from location to location and use local computers, and that's partly to ensure the hidden
directory stays hidden!) - does mean I sometimes run into issues that some hyper-networked system with ZB of storage
don't even notice. 

You will not loose your logbook data if you have access rights to the file system where the "elogd" program writes it's data.

The easiest way is to edit there password file directly and then restart "elogd".

But even if you do not dare to edit the files directly, you still can solve the issue from the web interface:

• Create a new account, e.g. user "admin2"
• While logged in as "admin", make this user an administrator: go to "Change config file", add "Admin user = admin, admin2"
• Now log off and then login as "admin2"
• Check that you can do administration, then remove user "admin"
• Create a new user "admin" with proper "Full name" and "Email"
• Now log off and then login as "admin"
• Check that you can do administration, then remove user "admin2"

That should work. Good luck!