| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1828
|
Wed May 10 16:55:28 2006 |
 | Kevin McCarty | kmccarty@princeton.edu | Question | Linux | 2.6.1 | Re: Email notification question |
| 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. |
|
2218
|
Thu Apr 26 16:43:45 2007 |
 | Kevin McCarty | kmccarty@princeton.edu | Request | Linux | 2.6.3-1764 | Is there (planned) support for <A NAME> and <HR /> in ELCODE? |
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 |
|
2222
|
Fri Apr 27 08:56:10 2007 |
| Kevin McCarty | kmccarty@princeton.edu | Request | Linux | 2.6.3-1764 | Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE? |
| 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 |
|
142
|
Fri Sep 27 19:17:58 2002 |
 | Kevin Ellwood | kevin_ellwood@yahoo.com | Request | | | Increase attachment file size for elog command line client |
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 |
|
324
|
Wed May 7 16:54:26 2003 |
| Kevin Ellwood | kevin_ellwood@yahoo.com | Question | | | "Number Attachments =" not being read after upgrade |
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 |
|
326
|
Wed May 7 17:27:51 2003 |
| Kevin Ellwood | kevin_ellwood@yahoo.com | Question | | | Re: |
> > 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 |
|
66041
|
Tue Nov 11 16:45:04 2008 |
 | Kester Habermann | kester.habermann@gmail.com | Bug report | Other | 2.7.5 | elogd dies after receiving second SIGHUP |
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. |
|
67102
|
Mon Aug 15 11:36:02 2011 |
 | Kester Habermann | kester.habermann@gmail.com | Bug report | Other | 2.9.0 | SEGV after upgrade from 2.7.8 to 2.9.0 |
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
|
| Attachment 1: elog-2.9.0-dbx.txt
|
signal SEGV (no mapping at the fault address) in show_elog_list at line 19781 in file "elogd.c"
19781 message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;
(dbx)
(dbx) list
19781 message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;
19782
19783 if (filtering) {
19784 status = el_retrieve(msg_list[index].lbs, message_id, date, attr_list, attrib, lbs->n_attr, text,
19785 &size, in_reply_to, reply_to, attachment, encoding, locked_by);
19786 if (status != EL_SUCCESS)
19787 break;
19788
19789 /* apply filter for attributes */
19790 for (i = 0; i < lbs->n_attr; i++) {
(dbx) print index
index = 0
(dbx) where
=>[1] show_elog_list(lbs = 0x1180200, past_n = 0, last_n = 0, page_n = 0, default_page = 1, info = (nil)), line 19781 in "elogd.c"
[2] interprete(lbook = 0xffbd89f8 "Galileo-Coord", path = 0xffbd8648 ""), line 27213 in "elogd.c"
[3] decode_get(logbook = 0xffbd89f8 "Galileo-Coord", string = 0xffbfe896 ""), line 27253 in "elogd.c"
[4] process_http_request(request = 0x13a4eb8 "GET /Galileo-Coord/", i_conn = 1), line 28001 in "elogd.c"
[5] server_loop(), line 28926 in "elogd.c"
[6] main(argc = 5, argv = 0xffbffb8c), line 29947 in "elogd.c"
(dbx) print n_msg
n_msg = 49
(dbx) print *msg_list
*msg_list = {
lbs = 0x1195dd0
index = 1667786092
string = "\001\017��-D"
number = 0
in_reply_to = 0
}
(dbx) print msg_list[index].lbs->el_index[msg_list[index].index].message_id
dbx: cannot access address 0x18da195b00
(dbx) print ms(dbx) [index].lbs->el_index[msg_list[index].index].message_id
(dbx) print msg_list[index].lbs
msg_list[index].lbs = 0x1195dd0
(dbx) print msg_list[index].lbs->el_index
msg_list[index].lbs->el_index = (nil)
(dbx) pr(dbx) g_list[index].lbs->el_index
(dbx) print *msg_list[index].lbs
*msg_list[index].lbs = {
name = ""
name_enc = ""
data_dir = ""
top_group = ""
el_index = (nil)
n_el_index = (nil)
n_attr = 0
pwd_xml_tree = (nil)
}
(dbx) print msg_list[1].lbs
msg_list[1].lbs = (nil)
(dbx) print msg_list[2].lbs
msg_list[2].lbs = (nil)
(dbx) print msg_list[3].lbs
msg_list[3].lbs = (nil)
(dbx) exit
|