Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 132 of 806  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  113   Fri Aug 16 10:14:19 2002 Warning Stefan Siegelssiegel@lucent.comBug report  Problem with konqueror and pulldown menu (in config menu)
Hi ,

currently I am running Elog 2.1.1; when using a konqueror browser (ver. 
2.2.1, kde 2.2.1) the admin user cannot access in the Config menu the Login 
infos for other users except himself. The pulldown menu "Select user" is 
shown, but when the admin selects another user the info fields (Login name, 
full name, email) are not updated. They still show the attribute values for 
the admin user himself.

Is there a solution available?
Thanks (also for this very useful tool) and regards,

Stefan
  116   Fri Aug 16 11:21:20 2002 Question Stefan Siegelssiegel@lucent.comQuestion  documentation fro elconv
Hi,

is there a documentation for the elconv tool available?

Regards,

Stefan
  134   Wed Sep 11 18:37:27 2002 Warning Stefan Siegelssiegel@lucent.comBug fix  Error with not existing user name
Hi,

Elogd v. 2.1.2:

When trying to acces a password protected Log (global password file) with a 
non existing username one gets the response : cannot open file : <pw 
filename>

Better would be a message like: wrong user or password!

Regards,

Stefan
  135   Wed Sep 11 18:44:51 2002 Warning Stefan Siegelssiegel@lucent.comBug report  Icons for sorted entries
Hi,

when do a search and then sorting the outcome of the search via clicking on 
an attribute (to sort it in descending or vice versa order) there should an 
icon be displayed (up.gif or down.gif). But the icons could not be found due 
to a wrong path to the gif files: 

/elog/config//themes/default/up.gif 

Be aware of the two slashes!! Should only be one.

Best regards,


Stefan
  1279   Wed Jul 20 08:32:06 2005 Idea Stefan Rudatsr@smartnd.comQuestionWindows2.5.4-3Cannot stat() config file
Hi

Elog runs now for serveral month without any problem at a Windows 2000 server.
I must change the access rights for all Folders, remove the user everyone and set the
Rights only to defined groups .
Now I can see following Event ID

Event Type: Information
Event Source: ELOG
Event Category: None
Event ID: 0
Date: 20.07.2005
Time: 08:14:24
User: N/A
Computer: SNDSRV1
Description:
The description for Event ID ( 0 ) in Source ( ELOG ) cannot be found.
The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Cannot stat() config file; No such file or directory.

My question now. Have someone see the same Problem ?
It this is a access right problem How to set up the access rights for Elog
Elog folders ?

Bye
  42   Mon Jul 1 10:31:31 2002 Reply Stefan Rittstefan.ritt@psi.chBug fix  Re: strage colors when only 'cmd=Search' is given as command
> Try this URL
> 
> http://midas.psi.ch/elogdemo/Forum/?cmd=Search

Ok, has been fixed. Will be included in the next version.
  43   Mon Jul 1 10:32:28 2002 Reply Stefan Rittstefan.ritt@psi.chBug fix  Re: last?? links in threaded mode
> The mode (i.e. summary, threaded, full) should be kept for the
> last??? and past??? links on a page.
> 
> For instance:
> 
> http://midas.psi.ch/elogdemo/Linux/last10?mode=threaded
> 
> The last20 link on this page should also be in threaded mode.

Has been fixed. Will be included in next version.
  44   Mon Jul 1 10:36:47 2002 Reply Stefan Rittstefan.ritt@psi.chInfo  Re: Admin password
> I want to set up eLogs for a class w/out the need for passwords. But, at the
> same time, I don't want the students to change the config file. I tried
> setting up a global password, but am having some difficulty with the syntax
> I suppose I could remove the config command from the menu and edit the file
> using Pico, but that would require a better memory than I have...
> 
> ******************
> 
> usage: elogd [-p port] [-h hostname] [-D] [-c file] [-r pwd] [-w pwd] [-a
> pwd] [-l logbook]
> 
>        -p <port> TCP/IP port
>        -h <hostname> TCP/IP hostname
>        -D become a daemon
>        -c <file> specify configuration file
>        -v debugging output
>        -r create/overwrite read password in config file
>        -w create/overwrite write password in config file
>        -a create/overwrite admin password in config file
>        -l <logbook> specify logbook for -r and -w commands
> 
>        -k do not use keep-alive
> 
> [root@eMonster elog]# elogd -a youtheman
>           
> Must specify a lookbook via the -l parameter.

Nearly correct, just follow the note: specify a logbook via the -l parameter.
So if you logbook is called "linux", you enter

elogd -a youtheman -l linux
ELOG V3.1.5-3fb85fa6