| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66628
|
Tue Nov 24 10:38:26 2009 |
 | Bertram Metz | Bertram.Metz@gefanuc.com | Question | Other | 2.7.7 | elogd.cfg for this forum | Hi Stefan,
I'm interested in the current configuration file for this discussion forum. Could you please post it to the
'config examples' logbook?
Thanks,
Bertram |
|
66629
|
Thu Nov 26 13:12:23 2009 |
 | Bertram Metz | Bertram.Metz@gefanuc.com | Question | Other | 2.7.7 | Re: elogd.cfg for this forum | > Hi Stefan,
>
> I'm interested in the current configuration file for this discussion forum. Could you please post it to the
> 'config examples' logbook?
>
> Thanks,
> Bertram
Sure, here it is! |
| Attachment 1: elogd.cfg
|
[Forum]
; general options
Password file = <xxx>
CSS = forum.css
Login expiration = 1000
Allow delete = stefan
Self register = 2
Comment = Discussion forum about ELOG
Display mode = threaded
Guest menu commands = Back, Find, Login, Help
Guest list menu commands = Find, Login, Help
Number Attachments = 1
Message comment = <img src=icons/icon6.gif> Please enter only serious messages here, for testing use the <a href="../Linux+Demo">Linux</a> Logbook:
Entries per page = 8
Reverse sort = 1
Restrict edit = 1
; Attributes
Attributes = Icon, Author, Author Email, Category, OS, ELOG Version, Subject
Options Category = Info, Bug report, Bug fix, Question, Request, Comment, Other
Style Category Info = background-color:lightblue;color:red
IOptions Icon = icon1.gif, icon2.gif, icon3.gif, icon4.gif, icon5.gif, icon6.gif, icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
MOptions OS = Linux, Windows, Mac OSX, All, Other
Icon comment icon1.gif = Entry
Icon comment icon2.gif = Reply
Icon comment icon3.gif = Idea
Icon comment icon4.gif = Warning
Icon comment icon5.gif = Question
Icon comment icon6.gif = Cool
Icon comment icon7.gif = Smile
Icon comment icon8.gif = Angy
Icon comment icon12.gif = Blink
Icon comment icon13.gif = Disagree
Icon comment icon14.gif = Agree
Required Attributes = Author, Author Email, Subject, Icon, OS, ELOG Version, Category
Preset on reply subject = Re: $subject
Thread display = $subject, posted by $author on $Entry time
RSS title = $subject, posted by $author on $Entry time
Thread icon = Icon
Date format = %B %d, %Y
Preset Author = $long_name
Preset Author Email = $user_email
Preset on reply Author = $long_name
Preset on reply Author Email = $user_email
Preset on reply Icon = icon2.gif
Locked Attributes = Author
Quick filter = Date, Category, Subtext
; Combine attributes into singles lines
Format Author = 1
Format Author email = 1, attribname, attribvalue, 30, 256
Format OS = 1
Format ELOG Version = 1, attribname, attribvalue, 10, 10
Format Subject = 0, subjname, subjvalue
; Email notification
Email message body = 1
Display Email recipients = 0
Omit Email to = 1
Use Email from = noreply@psi.ch
Use Email subject = ELOG Forum: "$Subject" posted by $Author
Email encoding = 4
|
|
66762
|
Mon Mar 15 09:29:11 2010 |
| Bertram Metz | Bertram.Metz@ge.com | Question | Windows | 2.7.8 | Invalid URL for groups beneath top groups in overview page | Hi,
I'm trying to implement top groups and started with the sample configuration shown in the 'Syntax of elogd.cfg' chapter of the documentation. But now I'm facing a problem with the links in the logbook selection page.
Here's my group configuration:
Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP
Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1
The selection page for the top groups is displayed correctly, but the URL for the groups beneath the top group is incorrect. The URL for the Linux PCs group for instance is http://localhost:8080/engineering/engineering/ . The URLs for the logbooks within the Linux PCs groups is correct (e.g. http://localhost:8080/Debian/)
Has anybody an idea what's going wrong in y configuration?
Bertram |
| Attachment 1: elogd.cfg
|
[global]
Port=8080
Logbook tabs = 1
Expand selection page = 0
;Main tab = "Overview"
Use Lock = 1
Default encoding = 1
Resolve host names = 0
Logfile = elogd.log
Logging level = 3
Logout to main = 1
Options Author = BMetz
Admin user = BMetz
Password file = ./passwd
;Protect selection page = 0
Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP
Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1
[Red Hat]
Comment = Red Hat Logbook
Time format = %Y-%m-%d
[Debian]
Comment = Debian Logbook
Time format = %Y-%m-%d
[Mandrake]
Comment = Mandrake Logbook
Time format = %Y-%m-%d
[NT]
Comment = NT Logbook
Time format = %Y-%m-%d
[XP]
Comment = VR11/VP11
Time format = %Y-%m-%d
[Employees]
Comment = Employess
Time format = %Y-%m-%d
[Purchases]
Comment = Purchases
Time format = %Y-%m-%d
|
|
66764
|
Mon Mar 15 13:20:17 2010 |
 | Bertram Metz | Bertram.Metz@ge.com | Comment | Windows | 2.7.8 | Re: Invalid URL for groups beneath top groups in overview page |
| Stefan Ritt wrote: |
|
| Bertram Metz wrote: |
|
Hi,
I'm trying to implement top groups and started with the sample configuration shown in the 'Syntax of elogd.cfg' chapter of the documentation. But now I'm facing a problem with the links in the logbook selection page.
Here's my group configuration:
Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = NT, XP
Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
Show top groups = 1
The selection page for the top groups is displayed correctly, but the URL for the groups beneath the top group is incorrect. The URL for the Linux PCs group for instance is http://localhost:8080/engineering/engineering/ . The URLs for the logbooks within the Linux PCs groups is correct (e.g. http://localhost:8080/Debian/)
Has anybody an idea what's going wrong in y configuration?
Bertram
|
Thanks for reporting this bug. I fixed it in the intermediate release 278-4 which is ready for download.
|
Thanks for the quick bug fix.
Bertram |
|
69864
|
Thu Jan 23 11:32:05 2025 |
 | Arjan Hulsbosch | Arjan.Hulsbosch@ext.esa.int | Bug report | Linux | Windows | Mac OSX | All | Other | 3.1.5 | Webserver authentication may cause redirect loop | If
- Elog is configured to use webserver authentication, and
- the user reported by the webserver does not exist in the password file, and
- the "Guest Menu commands" configuration is set in "elogd.cfg", and
- a logbook is accessed,
then Elog returns with a redirect (302) to the logbook itself, causing the loop.
The fix here is to remove the "Guest Menu commands" configuration from "elogd.cfg".
Source code location: https://bitbucket.org/ritt/elog/src/30ada1df634529c8011c27275c52a05b01b7b3d6/src/elogd.cxx#lines-27599 |
|
68839
|
Tue Sep 11 19:46:40 2018 |
| Allen Tuttle | AllenEmail@wavecable.com | Bug report | Linux | 3.1.3 | Compile issues on Fedora withe current elog source | Tried compiling on FC27 and 28, both result in binaries but with serious issues; writing data larger than then allowed.
Example output:
make
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Imxml -DHAVE_SSL -c -o mxml.o mxml/mxml.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Imxml -DHAVE_SSL -w -c -o crypt.o src/crypt.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Imxml -DHAVE_SSL -w -c -o regex.o src/regex.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Imxml -DHAVE_SSL -c -o strlcpy.o mxml/strlcpy.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Imxml -DHAVE_SSL -o elog src/elog.c mxml.o crypt.o regex.o strlcpy.o -lssl
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Imxml -DHAVE_SSL -w -c -o auth.o src/auth.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Imxml -DHAVE_SSL -o elogd src/elogd.c auth.o mxml.o crypt.o regex.o strlcpy.o -lssl
src/elogd.c: In function ‘el_retrieve’:
src/elogd.c:4503:26: warning: ‘%s’ directive writing up to 255 bytes into a region of size between 1 and 256 [-Wformat-overflow=]
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~
src/elogd.c:4503:4: note: ‘sprintf’ output between 1 and 542 bytes into a destination of size 256
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.c: In function ‘el_retrieve_attachment.part.30’:
src/elogd.c:4764:26: warning: ‘%s’ directive writing up to 255 bytes into a region of size between 1 and 256 [-Wformat-overflow=]
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~
src/elogd.c:4764:4: note: ‘sprintf’ output between 1 and 542 bytes into a destination of size 256
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.c: In function ‘el_submit.constprop’:
src/elogd.c:4894:29: warning: ‘%s’ directive writing up to 255 bytes into a region of size between 1 and 256 [-Wformat-overflow=]
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~
src/elogd.c:4894:7: note: ‘sprintf’ output between 1 and 542 bytes into a destination of size 256
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.c: In function ‘el_submit’:
src/elogd.c:4894:29: warning: ‘%s’ directive writing up to 255 bytes into a region of size between 1 and 256 [-Wformat-overflow=]
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~
src/elogd.c:4894:7: note: ‘sprintf’ output between 1 and 542 bytes into a destination of size 256
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.c: In function ‘el_retrieve.constprop’:
src/elogd.c:4503:26: warning: ‘%s’ directive writing up to 255 bytes into a region of size between 1 and 256 [-Wformat-overflow=]
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~
src/elogd.c:4503:4: note: ‘sprintf’ output between 1 and 542 bytes into a destination of size 256
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.c: In function ‘el_retrieve.constprop’:
src/elogd.c:4503:26: warning: ‘%s’ directive writing up to 255 bytes into a region of size between 1 and 256 [-Wformat-overflow=]
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~
src/elogd.c:4503:4: note: ‘sprintf’ output between 1 and 542 bytes into a destination of size 256
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.c: In function ‘el_retrieve.constprop’:
src/elogd.c:4503:26: warning: ‘%s’ directive writing up to 255 bytes into a region of size between 1 and 256 [-Wformat-overflow=]
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~
src/elogd.c:4503:4: note: ‘sprintf’ output between 1 and 542 bytes into a destination of size 256
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.c: In function ‘show_download_page’:
src/elogd.c:14775:32: warning: ‘%s’ directive writing up to 255 bytes into a region of size between 1 and 256 [-Wformat-overflow=]
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~
src/elogd.c:14775:10: note: ‘sprintf’ output between 1 and 542 bytes into a destination of size 256
sprintf(file_name, "%s%s%s", lbs->data_dir, lbs->el_index[index].subdir, lbs->el_index[index].file_name);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.c: In function ‘search_last_reply’:
.
.
.
Anyone aware of a cure? |
|
Draft
|
Wed Sep 12 15:20:11 2018 |
| Allen Tuttle | AllenEmail@wavecable.com | Bug report | Linux | 3.1.3 | Re: Compile issues on Fedora withe current elog source | I don't see the update on elog/download/tar/.
Do you keep builds elsewhere, perhaps on get or sourceforge?
| Stefan Ritt wrote: |
|
This warning is triggered by the use of the sprintf() funciton, which can write beyond the boundary of the destination string. I replaced it by snprintf(), which should make the compiler happy. Code is committed. Unfortuantely I have no FC27 here, so if there is still some waring with the current code, please post the full warning list here.
Stefan
|
|
|
68842
|
Wed Sep 12 15:25:07 2018 |
| Allen Tuttle | AllenEmail@wavecable.com | Bug report | Linux | 3.1.3 | Re: Compile issues on Fedora withe current elog source | I would like to try the new code, I don't see it on elog/download/tar/.
Do you keep updates elsewhere like on get or sourceforge?
| Stefan Ritt wrote: |
|
This warning is triggered by the use of the sprintf() funciton, which can write beyond the boundary of the destination string. I replaced it by snprintf(), which should make the compiler happy. Code is committed. Unfortuantely I have no FC27 here, so if there is still some waring with the current code, please post the full warning list here.
Stefan
|
|
|