Yes, you are correct, I did simply take a sample page from logs and tinker with the html and css file, with the changes enumerated previously.  I have attached the tweaked sample html elog log page and css file, along with a few of the standard elog png files to complete the page with some semblance of the normal display.

 I would like to be notified by email of some logbook entries regardless of whether the user has chosen to suppress email or not.

This way I will always be aware of new entries, and users will still have the option of notifying a larger group of other users, or not.

As far as I can tell, presently the Suppress Email checkbox overrides Email All.

It would be very cool to be able to select Full from the view menu and then scroll rapidly through all entries looking for that high res photo of a SQUID chip I took two months ago. Presently the photos are all full size so the Full view is slow to load and it takes a lot of scrolling to navigate. Can you implement thumbnails in Full view, and also in the single entry view? Clicking on the thumbnail should, of course, open the full size image.

For now, I'm just using the wysiwyg html entry format and dropping images into the entry, then right-clicking to set a small image size. Clicking on the image gives me a new window with the full size image, which works great.

I hope you don't mind the barrage of suggestions, and thanks again.

I am using the CMS ELog remotely as a monitoring tool.  Information is compartementalized into dozens of containers.  I can create a find query URL, say last day, which then reloads every X minutes in Firefox.  When new ELog entries are made, then appear in the refresh and catch my attention.  But, my interests are somewhere between a single logbook and all logbooks.  If I choose all CMS logbooks for example for one day, I usually end up with > 200 entries. 

In short, I would like the ability to:

1) Select from the list of available logbooks when doing a search

2) Have more canned choices from smaller time frames, such as 1 hour or at least one shift (8 hours).

I do not see how to do this in the current elogd.cfg syntax instructions.

Thanks, Alan

Hi Stefan,

Is it possible to derive the time in a 'date/time' attribute from the Elog server?
We would like all our entries in GMT/UTC time and unfortunately as the time is currently derived from the client machines there are often entry descrepancies if the regional settings are not set correctly.

The '$entry time' variable can be used but seems to put a 1970 date in the field so bears no relevancy to an 'Event' time?

I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?

Hope that makes a little sense?

Many thanks

Thanks for the response! BTW: I did get a notification - but thanks for the "personal heads-up"!

 I see. In that case, could you maybe please give a quick explanation what "List conditions" is supposed to do? In conjunction with your statement above I'm now thoroughly confused as to what it should/could be used for...

 Ah, that's an idea - I'll look into that. Thanks a mil for the suggestion!

Regards,

Thomas

> > 2) /etc/init.d/elogd: line 10: /etc/rc.d/init.d/functions: No such file or directory (I fixed this by commenting
> > out that line).
> > 
> > 3) Starting elogd: /etc/init.d/elogd: line 34: echo_success: command not found (Fixed by search/replace "echo_"
> > to "echo ").
> 
> The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the 
> typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package 
> which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian 
> updates are heavily old. Once elog gets managed inside Debian again, that should get better again, but until then 
> one has to follow 2) and 3) from above. If I would remove it, the Scientific Linux users would complain. 

I'm actually using elog on Debian and have been rolling my own ".deb" for a while now (starting with the old Debian
one and working my way up till 2.7.5). Maybe you could add the Debian /etc/init.d/elog script to the "contrib"
directory, with a suitable note in the README or something like that? That script has not changed in a long time and
is still functional - and doing so would make it easier for people who would like to install elog on a Debian (or
Debian-based, e.g. Ubuntu) system. I'll attach the script.

Regards,

Thomas