Re: Multi Logook Login, posted by Stefan Ritt on Wed May 6 16:03:56 2009
|
| Yoshio Imai wrote: | Hi, Stefan!
| Stefan Ritt wrote: | | If "password file = xxx" is however in each individual logbooks configuration, then you get "path=/<lobook>". You can check that by inspecting your browser's cookies. In that case the login name and password cookies are only sent to the URL for that specific logbook. I have not tested that extensively (different browsers, with/without Apache proxy), but if it works reliably, I will put this into the documentation. |
We had done so on your advice and in principle this works, but our experience has shown one problem:
We have separated our logbooks into different top groups because of the sheer number of them (i.e. experiment logbooks in one top group with logbook groups for the sub-categories, personal analysis logbooks in another top group etc.). Obviously, the experiment logbooks may share the same login, therefore we have put the "password file" statement into that top group's global section (otherwise, we would have to log on to every beamtime logbook individually, which can be cumbersome when comparing e.g. experiment settings between beamtimes). For the personal logbooks, of course, we use per-logbook-access (i.e. "password file" statement in the individual logbook sections) such that logging on to one's own logbook does not imply access to someone else's logbook. However, since the group/top group structure does not appear in the elog URLs, the cookies for the beamtime logbooks all have the path set to "path=/". This breaks the scheme again (I guess we have sort of "abused" the concept of top groups a little) and it is not possible to work in one of the experiment logbooks in parallel with one's own logbook without having to renew the login when switching the logbook.
Is it possible to modify the elogd such that it first checks if, among the cookies sent, there is one where the path corresponds to the path of the current logbook, and evaluate cookies with "path=/" only if no such cookie is found?
Yoshio |
I'm not sure if that helps. As soon as you have top groups, cookies have to use "path=/". I agree it would be best to use URLs in the form "http://<server>/<top group>/<logbook>", but cookies only support one level of directories (at least that was the case when I designed that a few years ago, I'm not sure if that's still the case). The only way around that is to give up top groups and run one elog server for each top group on a different port. |
Mail and logged in user , posted by Arno Teunisse on Sun May 10 22:18:56 2009
|
Hello
Was playing with elog. I send mail to the persons involved with a elog entrie. This mail produces something like this ( rather default) .
Logbook: Accelerator Message ID: 4 Entry time: 05/10/09 21:48:25 In reply to: 3
When I am logged in into elog , clicking on the Message ID 4 or 3 from the mail client , elog is started with the logged in user at that time and it's permissions. So instead of starting a new elog session ( and getting the guest permission ) I get the permission of the currently logged in user.( Could be the administrator / root) . The process will function correctly i no one is logged in into elog. I've tested this on a local machine, so I cannot say if the same happens when multiple machines are used. So, maybe it's a bug, maybe it's my testing configuration.
Do not know if i explained the problem clear enough, but is seems something that could be examined.
By the way : thanks for this great and free program.
|
can't send form , posted by larbi benouahi on Thu May 14 14:26:36 2009
|
Hi,
when i try to send a form after edit or create an entry i got this message : Connection closed by remote server
is there any idea
thanks |
|
Re: Mail and logged in user , posted by Stefan Ritt on Mon May 18 12:28:00 2009
|
| Arno Teunisse wrote: |
|
Hello
Was playing with elog. I send mail to the persons involved with a elog entrie. This mail produces something like this ( rather default) .
Logbook: Accelerator Message ID: 4 Entry time: 05/10/09 21:48:25 In reply to: 3
When I am logged in into elog , clicking on the Message ID 4 or 3 from the mail client , elog is started with the logged in user at that time and it's permissions. So instead of starting a new elog session ( and getting the guest permission ) I get the permission of the currently logged in user.( Could be the administrator / root) . The process will function correctly i no one is logged in into elog. I've tested this on a local machine, so I cannot say if the same happens when multiple machines are used. So, maybe it's a bug, maybe it's my testing configuration.
Do not know if i explained the problem clear enough, but is seems something that could be examined.
By the way : thanks for this great and free program.
|
This is not a bug, this is a feature! Once you log in to ELOG, your credentials are stored in cookies of your local browser. If you access a logbook entry, like via the link you in your email, you still use that credentials. If you clear all cookies of your browser, or log out explicitly from ELOG, then of course you will only get guest access. |
|
Re: Mail and logged in user , posted by Arno Teunisse on Tue May 19 23:43:20 2009
|
| Stefan Ritt wrote: |
|
| Arno Teunisse wrote: |
|
Hello
Was playing with elog. I send mail to the persons involved with a elog entrie. This mail produces something like this ( rather default) .
Logbook: Accelerator Message ID: 4 Entry time: 05/10/09 21:48:25 In reply to: 3
When I am logged in into elog , clicking on the Message ID 4 or 3 from the mail client , elog is started with the logged in user at that time and it's permissions. So instead of starting a new elog session ( and getting the guest permission ) I get the permission of the currently logged in user.( Could be the administrator / root) . The process will function correctly i no one is logged in into elog. I've tested this on a local machine, so I cannot say if the same happens when multiple machines are used. So, maybe it's a bug, maybe it's my testing configuration.
Do not know if i explained the problem clear enough, but is seems something that could be examined.
By the way : thanks for this great and free program.
|
This is not a bug, this is a feature! Once you log in to ELOG, your credentials are stored in cookies of your local browser. If you access a logbook entry, like via the link you in your email, you still use that credentials. If you clear all cookies of your browser, or log out explicitly from ELOG, then of course you will only get guest access.
|
Thanks Stefan
This was probably a buggy bug report. Was just testing things out on a local machine and cookies were send to the local machine. so the mail was using these cookies also.
In Practice this could never happen.
|
Memory leak in 2.76 elogd.exe, posted by jon huang on Thu Jun 4 17:51:50 2009 
|
Hi,
There's seems to be a memory leak with elogd.exe running windows. I had this problem with older version of elogd.exe, i've just upgrade to the latest and the problems still exist. I've had this issue with earlier versions. I've just upgrade elog to the latest 2.76 version. The memory leak still persist. I really appreciate if you or anyone here can help me resolve this issue.
Thank!
JH
|
|
Re: Memory leak in 2.76 elogd.exe, posted by Stefan Ritt on Fri Jun 5 10:51:17 2009
|
| jon huang wrote: |
|
Hi,
There's seems to be a memory leak with elogd.exe running windows. I had this problem with older version of elogd.exe, i've just upgrade to the latest and the problems still exist. I've had this issue with earlier versions. I've just upgrade elog to the latest 2.76 version. The memory leak still persist. I really appreciate if you or anyone here can help me resolve this issue.
|
ELOG has been carefully designed not to contain memory leaks. The server for this forum for example runs for months without problem:
[ritt@midas ~]$ ps aux | grep elogd
elog 1958 0.4 3.1 39412 32940 ? Ss May09 178:16 /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg
So if you have a problem, it must be specific to your installation. You should note that if you up- or download big attachents, memory gets allocated for some network buffers to contain these attachments. The buffer is kept to contain the largest attachment, it will never shrink. But once established, it will also not grow. If you see however a constant increase in memory consumption, I would appreciate if you tell me how you do this. Like which configuration you use, if you just read entries or also upload them, etc. etc. Once I can reproduce exactly your problem, I can try to fix it. |
|
I can not access the Logbook from another machine, posted by Gerardo Pruneda on Sun Jun 7 06:29:55 2009
|
I need some guidedance on how to access the logbook from another computer. I installed the logbook on a Windows server machine and started the logbook using port 81.
I can connect to the logbook on the same machine, but I can not access it from another machine on the same network.
I already confirm that the windows firewall is not enable. |
|