Re: Email notification question, posted by Kevin McCarty on Wed May 10 16:55:28 2006
|
| Stefan Ritt wrote: |
| Kevin McCarty wrote: | Hello,
I've just set up an ELog server for my research group. (Running on Debian, package version 2.6.1+r1642-1)
I have a question about the email notifications. I read through the config file documentation, but couldn't find the answer (maybe I am just unobservant\?) Is it possible to have the email notifications contain only the title of the log entry (as well as the usual attributes), but not the full text or any attachments? I have users who are worried about their email going over quota from ELog's emails, but who nevertheless would like some kind of notification when new log entries are posted.
Thanks in advance! |
Have a look at the option Email format = <n> |
Ah, thank you! Somehow I overlooked that. My apologies, and thanks for your very fast response. |
Is there (planned) support for <A NAME> and <HR /> in ELCODE?, posted by Kevin McCarty on Thu Apr 26 16:43:45 2007
|
Hello,
I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. This would be useful for long log messages in order to provide a table of contents and divide them into clear sections. If this support already exists, I'm afraid it is not obvious to me how to access it in ELCODE. If it does not yet exist, would you consider a patch for it?
As a related issue, to support <a name> usefully, it will also be necessary for ELCODE to support things like [url=#tag], which it currently converts to <a href = "http:///#tag"> instead the expected result of <a href = "#tag">.
(Please send me replies also by email at kmccarty AT princeton DOT edu, as I don't check this forum often.)
Thanks for writing ELOG; our group has been using it very productively on our server for the last few weeks.
best regards,
-- Kevin McCarty |
|
Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE?, posted by Kevin McCarty on Fri Apr 27 08:56:10 2007
|
| Stefan Ritt wrote: |
| Kevin McCarty wrote: | | I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. |
Very good idea. The horizontal line
is already implemented via [LINE] and the anchor tag will soon follow. |
Wonderful, thanks!
-- Kevin McCarty |
Increase attachment file size for elog command line client, posted by Kevin Ellwood on Fri Sep 27 19:17:58 2002
|
Hi,
I am having trouble modifying the elog client to allow larger attachment. I
have elogd configure for attchment sizes of 10Meg and I would like the
option to be able to use the elog client. Can anyone give me key points as
to how to go about doing this? I have tried but I must be missing something.
Also, as a suggestion, it might make sense to add a MAX_ATTACHMENT_SIZE def
in a common header file.
Thanks
Kevin |
|
"Number Attachments =" not being read after upgrade, posted by Kevin Ellwood on Wed May 7 16:54:26 2003
|
Hello
I have upgraded elog from version 2.2.4 to 2.3.6 and then entry "Number
Attachments =" is not being read. Looking at the changelog, I found that
"Number Attachments" has been removed in favor of "enable attachments". I
tried looking in the documentation but I can't find a discription of the way
in which multiple attachments are handled. Can someone give me a pointer?
Thanks
Kevin |
|
Re: , posted by Kevin Ellwood on Wed May 7 17:27:51 2003
|
> > I have upgraded elog from version 2.2.4 to 2.3.6 and then entry "Number
> > Attachments =" is not being read. Looking at the changelog, I found that
> > "Number Attachments" has been removed in favor of "enable attachments". I
> > tried looking in the documentation but I can't find a discription of the way
> > in which multiple attachments are handled. Can someone give me a pointer?
>
> Just upload one attachment at a time by hitting the "Upload" button, your
> message text stays there. Once you are finished, hit "Submit". Sorry, I
> thought this would be obvious, since most providers use this for their mail
> web interface.
No need to say sorry. It is probably obvious to pretty much everyone. -- It
the story of my life.
Thanks
Kevin |
elogd dies after receiving second SIGHUP, posted by Kester Habermann on Tue Nov 11 16:45:04 2008
|
elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates.
This was observed on Solaris 10 (SPARC).
The documentation states that elogd should re-read configuration after receiving SIGHUP. |
SEGV after upgrade from 2.7.8 to 2.9.0, posted by Kester Habermann on Mon Aug 15 11:36:02 2011 
|
Hello,
We've been using ELOG 2.6.5 to 2.7.8 for 4 years without any major problems.
Recently we upgraded to version 2.9.0 and since we've had the daemon frequently crash with SEGV.
I've detached debugging output from one time when ELOG the crashed. We've had many crashes
it was a different logbook each time. Platform is Solaris 10 5/08 on SPARC.
Has anyone else experienced problems with 2.9.0?
Best Regards
Kester
|