ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2054
|
Wed Nov 8 15:39:42 2006 |
 | deletoille | xavier.deletoille@synchrotron-soleil.fr | Bug report | Windows | 2.6.2-1746 | Re: checkbox |
| Stefan Ritt wrote: |
| deletoille wrote: | 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? |
I tried with V2.6.2-1741 and the problem was not there. It was fixed some time ago, so it should have worked in 1723 as well. Can you try the minimal example coming with the distribution, just by adding one MOptions attribute, like:
[global]
port = 8080
[demo]
Attributes = Author, Type
MOptions Type = Routine, Software Installation, Problem Fixed, Configuration, Other
and see if it work there? If it works correctly there but not with your config file, please send me your config file and I will try to reproduce the problem. |
You're right it works
It must be in my programming method
I share you my config file.
Thanks for your help |
| Attachment 1: Elog_08_11_06.doc
|
|
2053
|
Wed Nov 8 13:59:52 2006 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | All | 2.6.2-6 | Denial of Service Vulnerability of elog 2.6.2-6 | Dear ELOG users,
a denial of service vulnerability has been reported which affects all elog versions prior to 2.6.2-7. With a special request one can crash the elogd server, given that one has access either through a public read access or through an account. This vulnerability has been fixed in version 2.6.2-7. It is advised that all sensitive installations of ELOG are being updated.
Stefan Ritt |
|
2052
|
Wed Nov 8 13:07:31 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Other | 2.6.2-1714 | SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode |
| Steve Jones wrote: | | 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. |
The "cd /" is mandatory for daemons according to Unix standards. If a daemon gets started on an NFS subtree, that subtree cannot be unmounted anymore. Therefor it's required that all daemons cd to root, such that the NFS subtree can freely be mounted and unmounted. I therefore use absolute paths in all my statements of elogd.cfg. |
|
2051
|
Wed Nov 8 12:55:58 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | Other | 2.6.2-1714 | SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8) |
| Stefan Ritt wrote: |
| Steve Jones wrote: | BUG: In the initial comment section of elogd_fancy.cfg the line # This [global] section contains settings common to all logbooks 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 with a comment char; |
Acknowledged. The problem was that the section between the line # This [global] section contains settings common to all logbooks and the real [global] section was interpreted as the global section, and thus the "real" one was omitted. I changed the code now such that all lines starting with a '#' or ';' are completely skipped, that fixes the problem. The fix is contained in revision 1745.
| Steve Jones wrote: | ISSUE: The option Logbook dir = causes an enormous amount of problems, and this may be limited to elog installs that exist in NFS space (as opposed to local disk). If the default is left alone elogd appears to work fine; Try and override and the fun begins. The previous attached traces show that once going into daemon mode none of the logbook dirs can be found nor indexed. The workaround is to use the default "logbooks" dir. Perhaps the routine that creates the default (if not found) should be the same as the one that creates the override (?). |
That's weird. Have you tried to specify a full path for the logbook, like /nfs/some/directory ? The only difference of the daemon mode compared to the normal mode is that elogd does a cd to the root ('/'). If you specify logbook dir relative to the starting directory, like 'some/subdir', elogd will the try to access it under '/some/subdir', where it might not have read/write privileges. |
| Quote: | 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.
I'm putting this on hold for the time being as I now have test systems going into production. I'll be able to test next week.
|
|
|
2050
|
Wed Nov 8 08:20:34 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Other | 2.6.2-1714 | SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8) |
| Steve Jones wrote: | BUG: In the initial comment section of elogd_fancy.cfg the line # This [global] section contains settings common to all logbooks 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 with a comment char; |
Acknowledged. The problem was that the section between the line # This [global] section contains settings common to all logbooks and the real [global] section was interpreted as the global section, and thus the "real" one was omitted. I changed the code now such that all lines starting with a '#' or ';' are completely skipped, that fixes the problem. The fix is contained in revision 1745.
| Steve Jones wrote: | ISSUE: The option Logbook dir = causes an enormous amount of problems, and this may be limited to elog installs that exist in NFS space (as opposed to local disk). If the default is left alone elogd appears to work fine; Try and override and the fun begins. The previous attached traces show that once going into daemon mode none of the logbook dirs can be found nor indexed. The workaround is to use the default "logbooks" dir. Perhaps the routine that creates the default (if not found) should be the same as the one that creates the override (?). |
That's weird. Have you tried to specify a full path for the logbook, like /nfs/some/directory ? The only difference of the daemon mode compared to the normal mode is that elogd does a cd to the root ('/'). If you specify logbook dir relative to the starting directory, like 'some/subdir', elogd will the try to access it under '/some/subdir', where it might not have read/write privileges. |
|
2049
|
Wed Nov 8 07:59:01 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | V2.6.2-172 | Re: checkbox |
| deletoille wrote: | 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? |
I tried with V2.6.2-1741 and the problem was not there. It was fixed some time ago, so it should have worked in 1723 as well. Can you try the minimal example coming with the distribution, just by adding one MOptions attribute, like:
[global]
port = 8080
[demo]
Attributes = Author, Type
MOptions Type = Routine, Software Installation, Problem Fixed, Configuration, Other
and see if it work there? If it works correctly there but not with your config file, please send me your config file and I will try to reproduce the problem. |
|
2048
|
Tue Nov 7 09:22:52 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.6.2-1734 | Re: Bug? Password file location changed |
| David Spindler wrote: | | 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! |
That change was actually made in SVN revision 1708 on Aug. 1st, 2006, which was after the release of 2.6.2. So it will be made official in 2.6.3 and documented accordingly. |
|
2047
|
Tue Nov 7 08:38:57 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | latest | Re: Push button for Menue Command |
| An Thai wrote: | Dear Stefan,
in your documentation: ELOG - Syntax of elog.cfg I see two screenshots in the Themes section. The left one shows a layout with Push buttons on the Menue Command. I would like this layout and try to find information on W3C consortium how i can redesign the CSS file to realise the push button for hyperlink, but I cannot get an success there. Can you give more information how you made it?
Thank you in advance |
The push buttons in the menu were very old and have been removed long time ago. It is not possible to change this back via CSS, sorry. I updated the screen shots to more recent pictures. |
|