ELOG Forum

There is nothing to activate. As soon as you have some logbooks defined and you are using user level access ("password file = ..."), this page will show up.

66620

Tue Nov 17 19:04:16 2009

Re: Re: Re: Re: Subscribe to logbooks: Linux Demo, Database, etc.. regarding enable automatic email notifications

Stefan Ritt wrote:

Heinzmann wrote:

Stefan Ritt wrote:

Heinzmann wrote:

Hello Stefan,

how can I activate the part like: Subscribe to logbooks: Linux Demo, Database, etc.. regarding enable automatic email notifications

Just check the check boxes:

Isn't that obvious?

Sorry wrong question, I meant how can I configure this part?

There is nothing to activate. As soon as you have some logbooks defined and you are using user level access ("password file = ..."), this page will show up.

Sorry,

was my mistake, may I,m a little bit stressed.

cheers,

Michael

66621

Tue Nov 17 19:31:46 2009

Re: Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.

I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.

This is running under Win2K with SP4 as an automatic service on port 80.

I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.

If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.

I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash.

In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:

Hi,

I´m using 2.7.7 rev 2246 and tested it with my logbooks without any problems. But today I had no chance to reach them anymore. Strange.

Regards,

Michael

66622

Wed Nov 18 13:51:55 2009

soren poulsen

soren.poulsen@cern.ch

Question

Windows

2.7.6-2236

Re: Re: Elog & SSL Export to CSV , Problem

Stefan Ritt wrote:

Chuck Brost wrote:

Stefan, would it be possible to make the following change so that the document is not cached and at the same time it is possible to save it.

The change would entail replacing the "Pragma: no-cache" directive with an "Expires: " <HTTP-date> where <HTTP-date> is the same as Date header value. Please see section 14.21 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html

Hopefully there are no other side effects to this change.

ok, so I removed the "Pragma: no-cache". With IE it looks fine now, and if I repeat it two times it always gets is from elog and not from the cache due to the "Expires:" statement. The "no-cache" came from old days when some browsers did not yet support the "Expires" tag. I hope that this is better now, so let's see when we get the first complaints. The modification is in SVN revision 2265.

This seems to work fine.

66624

Fri Nov 20 19:32:22 2009

Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.

This is running under Win2K with SP4 as an automatic service on port 80.

I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.

If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.

I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash.

In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:

Sorry for the delay.

1: The offending log file.

66633

Tue Dec 1 14:20:04 2009