| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66123
|
Mon Dec 22 08:52:20 2008 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.5-2137 | Re: Tooltips for MOptions - not working? |
| Ben Shepherd wrote: |
|
Hi,
One of my logbooks is a fault reporting system; it emails a group of people when a fault is reported. There is an MOption 'Technical Groups', and I want to have a tooltip for each checkbox which shows who is referred to by each group name. However, individual tooltips for each MOption attribute don't seem to work. I've looked at the HTML code, and there's no 'title' attribute for the checkboxes, so it's not a browser problem. I've attached my config file. Any idea what's going wrong?
ben
|
The syntax for tooltips is
Tooltip <attribute option> = <tooltip>
but you have
Tooltip "<attribute>" "<attribute option>" = <tooltip>
which is not correct, but would make more sense, since you could have an attribut option being valid for several attributes. So I changed elogd to accept both syntax in revision 2158. Please note that you should not put "quotes" around attribute values or options. |
|
66124
|
Mon Dec 22 11:59:09 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.5-1 | Re: Display Revisions field in single entry but not in list view | The "Show Attributes" option is for the single entry view, while the "List Display" option is for the list view. So what you need is:
Attributes = Author, Type, Category, Subject
Show Attributes = Revisions
Locked attributes = Revisions
Subst on Edit Revisions = $Revisions $date by $long_name
List Display = ID, Date, Author, Type, Category, Subject |
|
66133
|
Tue Jan 6 15:11:53 2009 |
| Ben Shepherd | bjs54@dl.ac.uk | Question | Linux | 2.7.5-2137 | Re: Tooltips for MOptions - not working? |
| Stefan Ritt wrote: |
|
| Ben Shepherd wrote: |
|
Hi,
One of my logbooks is a fault reporting system; it emails a group of people when a fault is reported. There is an MOption 'Technical Groups', and I want to have a tooltip for each checkbox which shows who is referred to by each group name. However, individual tooltips for each MOption attribute don't seem to work. I've looked at the HTML code, and there's no 'title' attribute for the checkboxes, so it's not a browser problem. I've attached my config file. Any idea what's going wrong?
ben
|
The syntax for tooltips is
Tooltip <attribute option> = <tooltip>
but you have
Tooltip "<attribute>" "<attribute option>" = <tooltip>
which is not correct, but would make more sense, since you could have an attribut option being valid for several attributes. So I changed elogd to accept both syntax in revision 2158. Please note that you should not put "quotes" around attribute values or options.
|
Thanks! I got rid of the quotes around everything, and it works now.
ben |
|
66137
|
Fri Jan 9 10:41:20 2009 |
| Niklas | niklas@hoglund.pp.se | Bug report | Linux | 2.7.5 2142 | Re: Elogd crashes with: *** stack smashing detected *** |
| Stefan Ritt wrote: |
|
| Niklas wrote: |
|
Stefan,
perhaps there should be something like the bold text below in elogd.c:
int process_http_request(const char *request, int i_conn)^M
...
/* extract cookies */^M
if ((p = strstr(request, "Cookie:")) != NULL) {^M
p += 6;^M
do {^M
p++;^M
while (*p && *p == ' ')^M
p++;^M
strlcpy(str, p, sizeof(str));^M
for (i = 0; i < (int) strlen(str); i++)^M
if (str[i] == '=' || str[i] == ';')^M
break;^M
if (str[i] == '=') {^M
str[i] = 0;^M
p += i + 1;^M
for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' && i < (int) sizeof(cookie); i++)
cookie[i] = *p++;
...
|
Wow, where did you get that long cookie from? Certainly not from elogd. You must run elogd under Apache, and have some other service next to it on your server which distributes this long cookies, that's why other people did not experience this problem yet. I appreciate your fix. It's alwasy nice to see users not only complain about things, but try to fix them. Your fix is almost correct, you need a
i<(int) sizeof(cookie)-1
since there is the trailing zero for terminating the cookie string. I applied your fix to SVN revision #2146.
|
Just noticed that this fix does not work. Elog cookies e.g. "upwd" may be after other long cookies its not seen, as now it stops reading the cookie-string after 256 chars. There needs to be something that goes through the cookies and saves only elog cookies... Would probably be better if you code that, if you have time =D
BR, niklas |
|
66139
|
Fri Jan 9 22:40:59 2009 |
 | Devin Bougie | dab66@cornell.edu | Question | Linux | 2.7.5 | ELOG scalability | Hi, All. We have been successfully using ELOG in a limited deployment for a couple years now. However, we are about to embark on a new project that could run for up to 10 years, and are wondering what sort of scalability we can expect from ELOG.
Are there any problems we can expect to run into as the number of entries grow? I see in a previous thread that "elog runs fine for a few 10000 entries. At 100000 entries it starts getting slow." Is this still the case, or have any improvements been made? What sort of problems would we expect to run into? Any examples of existing large deployments would be very useful.
Many thanks,
Devin
|
|
66140
|
Sat Jan 10 09:58:43 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.5 | Re: ELOG scalability |
| Devin Bougie wrote: |
|
Hi, All. We have been successfully using ELOG in a limited deployment for a couple years now. However, we are about to embark on a new project that could run for up to 10 years, and are wondering what sort of scalability we can expect from ELOG.
Are there any problems we can expect to run into as the number of entries grow? I see in a previous thread that "elog runs fine for a few 10000 entries. At 100000 entries it starts getting slow." Is this still the case, or have any improvements been made? What sort of problems would we expect to run into? Any examples of existing large deployments would be very useful.
|
The above made statement is not true any more. Mainly due to the large CERN experiments, some speed improvements have been made in late 2007. So elog runs fine at least up to 100000 entries. The startup time might be a bit slow, since it parses all entries there, but beyond the maybe 20s startup time, there is not a big difference when browsing entries. The only peoblem left is if you try to search some text through 100000 entries, this could be a bit slow. I have not tried anhything beyond 100000 entries, because this was not requested so far. If logooks become too big, the entreis could be split into several logbooks. Even if there are several logbooks with 100000 entries each, the access time should not be slower than if there would be one logbook with 100000 entries. |
|
66147
|
Mon Jan 12 23:36:17 2009 |
| Michael Ambrus | ambrmi09@gmail.com | Question | Linux | 2.6.3 | SMTP problems - Error sending Email via "smtp.glocalnet.net" | Hello, I'm having problems with e-mail notifications.
When I try submitting a new post, I get the following error:
Error sending Email via "smtp.glocalnet.net"
The error message doesn't give a lot of hints...
My config file contains the following lines:
[global]
SMTP host = smtp.glocalnet.net
SMTP username = rhj764h@tninet.se
SMTP Password = xxx
...
[BugZ]
...
Email All = somebody@gmail.com
Use Email From = theproject@kato.homelinux.org
The password was created by invoking elogd with the -t option containing the true password. I've tried enter the correct password manually in the config, but the error message is the same.
Below follows a cut&paste of the console output when invoking with the -v option (addresses manually edited to avoid spam):
Email ALL to somebody@gmail.com
timezone: -3600, offset: 3600
Email from theproject@kato.homelinux.org to somebody@gmail.com, SMTP host smtp
.glocalnet.net:
220 mta3.glocalnet.net ESMTP Service ready
EHLO kato.homelinux.org
250-mta3.glocalnet.net
250-DSN
250-8BITMIME
250-PIPELINING
250-HELP
250-AUTH=LOGIN
250-AUTH LOGIN CRAM-MD5 PLAIN
250-X-CP-DELIVER-AFTER
250-DELIVERBY 300
250 SIZE
==== Return ================================
HTTP/1.1 302 Found
Server: ELOG HTTP 2.6.3-1762
Connection: Keep-Alive
Keep-Alive: timeout=60, max=10
Location: http://kato.homelinux.org/elog-tinker/BugZ/6?error=Error+sending+Email
+via+<i>"smtp.glocalnet.net"</i>
Content-Length: 20
I can't make any sense of this. Please advise.
Regards
/Michael Ambrus
|
|
66148
|
Tue Jan 13 00:14:37 2009 |
 | Michael Ambrus | ambrmi09@gmail.com | Question | Linux | 2.7.5-2130 | Re: SMTP problems - Error sending Email via "smtp.glocalnet.net" |
| Michael Ambrus wrote: |
|
Hello, I'm having problems with e-mail notifications.
When I try submitting a new post, I get the following error:
Error sending Email via "smtp.glocalnet.net"
The error message doesn't give a lot of hints...
My config file contains the following lines:
[global]
SMTP host = smtp.glocalnet.net
SMTP username = rhj764h@tninet.se
SMTP Password = xxx
...
[BugZ]
...
Email All = somebody@gmail.com
Use Email From = theproject@kato.homelinux.org
The password was created by invoking elogd with the -t option containing the true password. I've tried enter the correct password manually in the config, but the error message is the same.
Below follows a cut&paste of the console output when invoking with the -v option (addresses manually edited to avoid spam):
Email ALL to somebody@gmail.com
timezone: -3600, offset: 3600
Email from theproject@kato.homelinux.org to somebody@gmail.com, SMTP host smtp
.glocalnet.net:
220 mta3.glocalnet.net ESMTP Service ready
EHLO kato.homelinux.org
250-mta3.glocalnet.net
250-DSN
250-8BITMIME
250-PIPELINING
250-HELP
250-AUTH=LOGIN
250-AUTH LOGIN CRAM-MD5 PLAIN
250-X-CP-DELIVER-AFTER
250-DELIVERBY 300
250 SIZE
==== Return ================================
HTTP/1.1 302 Found
Server: ELOG HTTP 2.6.3-1762
Connection: Keep-Alive
Keep-Alive: timeout=60, max=10
Location: http://kato.homelinux.org/elog-tinker/BugZ/6?error=Error+sending+Email
+via+<i>"smtp.glocalnet.net"</i>
Content-Length: 20
I can't make any sense of this. Please advise.
Regards
/Michael Ambrus
|
An update:
I got rid of the version from the Ubuntu repo and installed the latest source release instead (2.7.5-2130).
The error is now a little bit different:
Error sending Email via "smtp.glocalnet.net": Syntax error in parameters or arguments to MAIL command
A snippet from the console output:
250-DELIVERBY 300
250 SIZE
AUTH LOGIN
`±è· ♦Username:
cmhqNzY0aEB0bmluZXQuc2U=
Password:
ajh6N2E4
235 LOGIN authentication successful
MAIL FROM: theproject@kato.homelinux.org
501 Syntax error in parameters or arguments to MAIL command
==== Return ================================
BR /Michael |
|