If you use an attribute "Entry" then the internal variable "entry time" will expand to the last value of
"$Entry"+" time", e.g. if you use it in "Thread display = $entry time, ..."

One side effect is, that the logbook selection page defaults to use
Last submission = $entry time by $author
Which then expands to an undesired result.

This is not really a bug, rather something you'll need to keep in the back of your mind.

A query to a logbook can crash the demon.

Query:
https://pc8059.psi.ch:444/SwissFEL+Injector/?jcmd=Find&m0a=10&d0a=27&y0a=2011&npp=1&reverse=0

gdb dump:
SSLServer listening on port 444 ...

Program received signal SIGSEGV, Segmentation fault.
show_elog_list (lbs=0xae72618, past_n=0, last_n=0, page_n=0, default_page=1, info=0x0) at src/elogd.c:20797
20797         message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;

After registering, elog displays a page with the message:

     Error: Command "Config" is not allowed for user ""

However, the registration is successful. This causes confusion, and results in users registering multiple times.

In the elogd.conf file, I have the directive:

     Allow Config = bergman

Any suggestions?

 Well done Mike!

One result is that I've also learnt things, realised that there are some known unknowns and perhaps some unknown unknowns in my

understanding of Elog.

 Got it to work, manipulating the files was not that hard once I got over the FEAR factor.  Good luck with the speed of light thing.

 Perfect! I didn't not know there was RSS support. I will probably use something like rss2email, but this is exactly what I needed. Thanks!

What we do is use the RSS feed of elog. This gives you nice summaries without going through your email inbox. Most browsers have RSS readers, there are also tons of stand-alone programs for that. Attached is a screenshot from the Google Reader subscribed to this logbook and to the "contributions' logbook. You see nice one-line summaries, you can expand them, and you can go directly to the logbook if you click on the arrow. The second image is from the Firefox using what they call "live bookmarks", but it's basically a RSS reader.

To make this work, I installed the RSS extension of Google Chrome (Firefox has this under "Bookmarks"/"Subscribe to this page"), then go to the elog page, then click on the RSS icon, then clicked on "Subscribe to this" via Google Reader. Just a few clicks.

Hope this is what you want.

- Stefan

We have about 10 logbooks running on the same Elog that all get fair use. Many people have turned off new entry emails because they were filling up inboxes, but are still interested in what's new. I saw the option to add "?last=1" to the start page, although I'm afraid using it might cause confusion over how to get to the older posts.

I was trying to figure out a way of creating a "digest" of sorts, a list of entry subjects posted in the past day or week, something similar to what's generated by "?last=1?mode=threaded", but for every logbook (similar layout to the selection page with nested logbooks). This could either be a page, or a regular email.

Is there way to generate such a cross-logbook page? What about a scheduled email formatted based on a given filter?

PS: The elog has been invaluable to us, a big thanks to all involved!