Re: Bug? Password file location changed, posted by David Spindler on Fri Nov 3 14:40:36 2006
|
[quote="Steve Jones"][quote="David Spindler"][quote="David Spindler"]I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the
elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command
prompt that it was creating a new empty password file in a different location.
|
|
Re: Bug? Password file location changed, posted by Stefan Ritt on Tue Nov 7 09:22:52 2006
|
[quote="David Spindler"]Thanks. I checked the changelog and the documentation for any such changes but did not see them. I just looked again, and still
do not see them. Anyway, I know what to expect, now, and will adjust. Again, thanks![/quote]
|
|
Re: checkbox, posted by Stefan Ritt on Wed Nov 8 07:59:01 2006
|
[quote="deletoille"]I found a small Bug when I create an entry. I activate a checkbox (attachement1) but when I upload a file, the activation disappears
(attachement 2). I have to activate again the checkbox.
Is it something I can do?[/quote]
|
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Stefan Ritt on Wed Nov 8 08:20:34 2006
|
[quote="Steve Jones"]BUG: In the initial comment section of elogd_fancy.cfg the line [CODE]# This [global] section contains settings common to all logbooks[/CODE]
is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup the port=8080 option. Taking
"[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine ignores *entire* lines starting |
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Steve Jones on Wed Nov 8 12:55:58 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]BUG: In the initial comment section of elogd_fancy.cfg the line [CODE]# This [global] section contains settings
common to all logbooks[/CODE] is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup
the port=8080 option. Taking "[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine |
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode, posted by Stefan Ritt on Wed Nov 8 13:07:31 2006
|
[quote="Steve Jones"]Very weird. No, I did not try an absolute path - but I did notice the attempt to "cd /" in the truss output. In fact, it was immediately
after that "cd /" test that things appeared to start not working - basically, elogd could not find anything.[/quote]
|
Re: checkbox, posted by deletoille on Wed Nov 8 15:39:42 2006 
|
[quote="Stefan Ritt"][quote="deletoille"]I found a small Bug when I create an entry. I activate a checkbox (attachement1) but when I upload a file, the
activation disappears (attachement 2). I have to activate again the checkbox.
Is it something I can do?[/quote]
|
ELOG Crash by many email address, posted by An Thai on Fri Jan 12 15:28:46 2007
|
Hello,
when I try to set above 112 email addresses in
|