| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66351
|
Wed May 6 16:03:56 2009 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5 | Re: Multi Logook Login |
| 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. |
|
67553
|
Fri Aug 16 12:01:56 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.9.2 | Re: Moving password file |
| UlfO wrote: |
|
Hi,
Is it possible to move a passwordfile from one E-log to another E-Log located on a different server without the need for users to register again?
Regards
/UlfO
|
Yes. Just make sure that both elog servers are not running when you move the password file. |
|
65981
|
Thu Sep 18 14:39:17 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | | Re: Moving individual messages in a thread |
| Eoin Butler wrote: |
|
It is possible that the Move to... and Copy to... commands can be configured so that when they operate on a message that is part of a thread, that only that message will be moved, instead of the whole thread?
|
This has not been implemented on purpose. Assume you have a thread with
A
B
C
So A links to B, B links back to A and so on. If you would move now B into another logbook, A and C would point to an entry which does not exist any more. Furthermore, C may contain some sentences which are a reply to something which has been said in B. So even if the "Move To" mechanism would re-link A to C and C to A, the entry C would maybe make no sense any more if B is missing. That's why you only can move threads as a whole. If you want to move individual messages, don't use replies. You can actually disable the reply command in the configuration file. |
|
66373
|
Thu Jun 4 15:21:23 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.7.6-2191 | Re: Moving entry (and replies) from one log book to another | Hi Stefan,
Any possibility on this one?
David Pilgram.
> Hi Stefan,
>
> When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
> the entries' ID number(s) ($@MID@$). While it may not be good practice, we've referred to these numbers in
> cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
> your FAQ about marking of whole threads).
>
> In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
> ID number.
>
> Thanks,
>
> David Pilgram. |
|
66379
|
Fri Jun 5 11:29:43 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.6-2191 | Re: Moving entry (and replies) from one log book to another | > Hi Stefan,
>
> When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
> the entries' ID number(s) ($@MID@$). While it may not be good practice, we've referred to these numbers in
> cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
> your FAQ about marking of whole threads).
>
> In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
> ID number.
>
> Thanks,
>
> David Pilgram.
I have implemented this feature in revision 2205. You need to set the new flag "Preserve IDs = 1" in the
configuration. I have not tested this extensively, but I'm sure you will do it ;-) |
|
66380
|
Fri Jun 5 12:02:45 2009 |
 | David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.7.6-2191 | Re: Moving entry (and replies) from one log book to another | Thanks Stefan, Downloading shortly and I'll let you know ;-)
> > Hi Stefan,
> >
> > When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
> > the entries' ID number(s) ($@MID@$). While it may not be good practice, we've referred to these numbers in
> > cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
> > your FAQ about marking of whole threads).
> >
> > In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
> > ID number.
> >
> > Thanks,
> >
> > David Pilgram.
>
> I have implemented this feature in revision 2205. You need to set the new flag "Preserve IDs = 1" in the
> configuration. I have not tested this extensively, but I'm sure you will do it ;-) |
|
1191
|
Mon Jun 13 17:45:47 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | | Re: Moving eLog from Server to Server... |
| Charles Duncan wrote: | I am moving my eLog system from one server to another.
I moved all my log books, my /etc/elog.conf, and /usr/share/elog/elog.pwd file. Did I miss anything?
The Logbooks come up fine on the eLog list, but when I try to access them I get invalid user name...
Do I have to do some sort of conversion to move the pwd file from one server to another?
Or should I try using the sync command for the move? does sync also move the pwd file?? |
Of course you have to start elogd after you copied all files over, but I presume you did that. The password file itself does not need any conversion, it should work on both hosts fine. Cloning an elog logbook (via the "-C <url>") flag, does copy the password file if you enter "yes" to the according question. Have you checked the file permission of the password file? Maybe the user name elogd is running under has no read access to it. |
|
1192
|
Mon Jun 13 18:45:45 2005 |
| Charles Duncan | Charles@YorkU.CA | Question | Linux | | Re: Moving eLog from Server to Server... |
| Quote: |
| Stefan Ritt wrote: |
| Charles Duncan wrote: | I am moving my eLog system from one server to another.
I moved all my log books, my /etc/elog.conf, and /usr/share/elog/elog.pwd file. Did I miss anything?
The Logbooks come up fine on the eLog list, but when I try to access them I get invalid user name...
Do I have to do some sort of conversion to move the pwd file from one server to another?
Or should I try using the sync command for the move? does sync also move the pwd file?? |
Of course you have to start elogd after you copied all files over, but I presume you did that. The
password file itself does not need any conversion, it should work on both hosts fine. Cloning an elog logbook
(via the "-C <url>") flag, does copy the password file if you enter "yes" to the according question. Have you
checked the file permission of the password file? Maybe the user name elogd is running under has no read access
to it. |
|
I reinstalled elog on the new server and ran the clone (via the "-C <url>"), wow that is really slick. But unfortunately my passwords and user data were not transfered. I did say 'Y' when prompted to transfer the password info.
I think my problem is that one server is running 2.5.9 (or 2.6.0 beta, unstable, Debian) and my new server is running 2.5.5.3 (stable, UBUNTU).
Are the password files not compatible between the 2 versions?
All my logbook entries appear to be there in full.
btw: I am back leveling to 2.5.5.3 because I lose my last column on every log book view. |
|