Error while trying to change password (elogd 2.1.0), posted by Stefan Siegel on Mon Aug 12 11:01:51 2002
|
When logging in with a username and password; then trying to logout or
change password one gets the following message:
Error: Parameter value too big. Please increase VALUE_SIZE and recompile
elogd ; Please use your browser's back button to go back
(up to now I have not yet tried to recompile - may be it works then)
Regards,
Stefan |
Re: Error while trying to change password (elogd 2.1.0), posted by Stefan Siegel on Wed Aug 14 13:44:12 2002
|
> > When logging in with a username and password; then trying to logout or
> > change password one gets the following message:
> >
> > Error: Parameter value too big. Please increase VALUE_SIZE and recompile
> > elogd ; Please use your browser's back button to go back
> >
> > (up to now I have not yet tried to recompile - may be it works then)
>
> That's strange. This error should only occur if someone uses a user name or
> password with more than 256 characters, which I hope is not the case. Have
> you tried changing your password etc. in this forum? It also runs 2.1.0 on
> Linux.
>
> I made a version under
>
> http://midas/cgi-bin/cvsweb/~checkout~/elog/elogd.c?rev=2.67&content-
> type=text/plain
>
> which has improved error output for this problem, maybe this helps.
Hi,
changed the VALUE_SIZE from 256 to 512. That seems to fix the problem.
Regards,
Stefan |
|
Problem with konqueror and pulldown menu (in config menu), posted by Stefan Siegel on Fri Aug 16 10:14:19 2002
|
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 |
documentation fro elconv, posted by Stefan Siegel on Fri Aug 16 11:21:20 2002
|
Hi,
is there a documentation for the elconv tool available?
Regards,
Stefan |
|
Error with not existing user name, posted by Stefan Siegel on Wed Sep 11 18:37:27 2002
|
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 |
|
Icons for sorted entries, posted by Stefan Siegel on Wed Sep 11 18:44:51 2002
|
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 |
Cannot stat() config file , posted by Stefan Rudat on Wed Jul 20 08:32:06 2005
|
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 |
|
Re: strage colors when only 'cmd=Search' is given as command, posted by Stefan Ritt on Mon Jul 1 10:31:31 2002
|
> Try this URL
>
> http://midas.psi.ch/elogdemo/Forum/?cmd=Search
Ok, has been fixed. Will be included in the next version. |