> > Hi Stefan,
> > 
> > This has happened twice on this forum now, starting from Mon 23rd November.
> > 
> > Someone submits an entry (Me, 66625, Bertram Metz 66628)
> > I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
> > yourself.  My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.
> > 
> > Is this a bug, or some wierd affect of us forgetting to log out?
> > 
> > Regards,
> > 
> > David.
> 
> Thanks for pointing out this issue. This bug was introduced recently, when I tried to avoid the
> 
> Re: Re: Re: ...
> 
> in the subject line. I changed this now completely so that we can have
> 
> Preset on reply Author = $full_name
> Preset on first reply Subject = Re: $Subject
> 
> which fixes both things. The modification is in revision 2271.

Thanks Stefan!

Howdy and Thank you in advance.

       Can I limit an elog entry mails to only go to my e-mail, my supervisor and the person who is entering the elog entry.  I have the Elog server on Windows XP Pro running version 2.7.8.2282.

Thank you

Paul

 Thanks for the quick bug fix.

Bertram

 Sorry so long getting back to you, Stefan. Just wanted to say "thank you". This new function works great!

    Stefan,

I have checked it and it behaves exactly as you have described it. Perhaps this "double click"  has led me to that false conclusion ?

Great. Thanks Stefan. 

I also am already using the top groups. This is just to totally separate my work and home elog.....I have to admit I am really an elog addict. 

This elog and the idea behind it is absolutely  brilliant. Very useful, easy to maintain, migrate, configure, easy to use, versatile, etc...  Good on you all.

Cheers,

Behdad.

/* workaround for wong timezone under MAX OSX */
long my_timezone()
{
#if defined(OS_MACOSX) || defined(__FreeBSD__)
   time_t tp;
   time(&tp);
   return -localtime(&tp)->tm_gmtoff;
#else
   return timezone;
#endif
}

 BINGO! That was it - thank you! I've added the || defined(__OpenBSD__) in the place you described above and now the dates are correct. While I was at it, I also had a look at what other ifdefs there are for FreeBSD and the only other one I found was also in elogd.c:

#if defined (_BSD_VA_LIST_) && defined (__FreeBSD__)

I'm far from being a C programmer, but I did some quick and dirty compile tests with various ifdefs set and apparently, _BSD_VA_LIST_ is not set on OpenBSD, so I guess that this statement does not need modification. I will keep my eyes peeled for strange behaviour, though...

Cheerio,

Thomas

P.S.: One thing I noticed is that the OpenBSD variant of gcc throws these warnings when compiling elogd.c:

gcc -g -funroll-loops -fomit-frame-pointer -W -Wall -DHAVE_SSL -I../mxml -o elogd src/elogd.c crypt.o regex.o mxml.o strlcpy.o -lcrypto -lssl
/tmp//ccHhMZfy.o(.text+0xd2f): In function `int_vasprintf':
src/elogd.c:826: warning: vsprintf() is often misused, please use vsnprintf()
/tmp//ccHhMZfy.o(.text+0xae8): In function `xstrdup':
src/elogd.c:736: warning: strcpy() is almost always misused, please use strlcpy()
/tmp//ccHhMZfy.o(.text+0x13c7): In function `my_shell':
src/elogd.c:1197: warning: sprintf() is often misused, please use snprintf()
/tmp//ccHhMZfy.o(.text+0xf0ae): In function `el_correct_links':
src/elogd.c:5178: warning: strcat() is almost always misused, please use strlcat()

I'm not certain whether this is specific to this gcc variant, but I seem to remember that the OpenBSD folks added some extra warnings and suchlike as part of their overall code audit, so I thought I'd mention it.

 Yes thanks Stefan! It is working now.

Thanks again!