> Hi Stefan,
> 
> After 21.Oct, all the emails sent out by this discussion form now are addressed to
> 
> ELOG@ananke.jtan.com
> the name of the server my mails are sent to.
> 
> Before that the emails were addressed to 
> 
> ELOG@emix.psi.ch
> 
> Obviouisly my real email address is there, in the headers (as it would appear for a BCC)
> 
> The only consequence for me was these emails turned up in the wrong mailbox, but perhaps it has wider implications?

Indeed on Oct. 21st the SMPT server sending out emails from this forum has been changed. I checked my own mails coming 
from the forum, but I could not find any hint of what you describe above. The "From:" header contains "noreply@psi.ch" 
and the "To:" header is my email address. The "Received:" header contains our SMTP server, but you should not that field 
for filtering your email.

- Stefan

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. 

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.

Thanks,

David

Hi Stefan,

After 21.Oct, all the emails sent out by this discussion form now are addressed to

ELOG@ananke.jtan.com
the name of the server my mails are sent to.

Before that the emails were addressed to 

ELOG@emix.psi.ch

Obviouisly my real email address is there, in the headers (as it would appear for a BCC)

The only consequence for me was these emails turned up in the wrong mailbox, but perhaps it has wider implications?

Hi elog experts =)

Anyone know if it's possible to have access control per group-level?

For instance:

Group A = B,C   

Group B = LogA   

Group C = LogB, LogC      

Group C: Read password = abc

?

//NH

> Hello.
> 
> Please look at the entry 66525 of this forum (just 5 thread before this one):
> 
>  ->  chain.crt, posted by Gerhard Schneider on Thu Sep 3 21:55:52 2009         (66525)
>   |->    Re: chain.crt, posted by Stefan Ritt on Fri Sep 4 08:33:16 2009       (66526)
>   |->    Re: chain.crt, posted by Gerhard Schneider on Wed Oct 7 07:56:52 2009 (66556)
> 
> When you collapse the thread, it is collapsed to the 66526 instead of the 66556 (more recent)
> 
>   +      Re: chain.crt, posted by Stefan Ritt on Fri Sep 4 08:33:16 2009  
> 
> I guess it is because both 66526 and 66556 replies to the first entry. 
> I have the same problem with Elog v2.7.7-2246 and Windows. 
> 
> In general, it seems to work well only if you always reply to the last entry of a thread.
> 
>   Thank you.
> 
> 
> b.t.w. : is there any tip to always force reply to the last entry of a thread?

As the person who suggested this concept, I have to admit I've yet to think of a good way around this issue. 
Preventing "branching" is all very well, but sometimes it is relivent to have a branch (although I usually try to
avoid them).  Unless elog scans every possible branch to find where the latest entry, I cannot think of a
foolproof, practical scheme.

Hi Stefan,

I have a thread of 70 entries.  I added another entry, which was saved, but elog crashed.
It would restart, but crash every time I then tried to access that 71 entry thread.

By editing the yymmdda.log files to remove the latest entry, all was well again.
Add a test new entry (much smaller) also crashed elog as before.

If it is any help, this is the error message I caught on a console:

src/elogd.c:703: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
./log: line 1:  3123 Aborted    

Now I have got around this, by ending that thread with reference to a new one to continue, but is this to be
expected?  

If this is something (like memory allocation) that would have been in hiding from the start, I cannot imagine
that it is likely to be hit often enough to actually "bug fix" - it might, in any case, cause problems elsewhere.

 This is not really resolved, since "Subst" creates a new number on both "New" and "Reply". I would like "Subst" to create a new number only on "New" and preserve this number through replies throughout the thread. I would like to be able to say "Subst thread = #" to make a new number for the thread and combine it with "Subst on reply thread = $thread" to preserve the number on replies, but this does not work. Maybe someone has already done this ?

Soren