ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66336
|
Thu Apr 30 08:40:43 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.6 | Re: elogd runs by a user but not by root |
Dongwook Jang wrote: |
Hi,
I wonder how others manage this situation because deamons in /etc/init.d is excercuted by root. So I cannot run in /etc/init.d/elogd when the system starts up.
What do you think?
Thanks,
Dongwook
|
The normal situation is that elogd gets started by root under /etc/init.d/, then the configuration file contains "Usr = elog" and "Grp = elog", so after it has been started as root, the program falls back to the "elog" user, which only has restricted rights.
|
66337
|
Thu Apr 30 08:48:01 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2185 | Re: Database Like - ELOG Format |
mike cianci wrote: |
Stefan,
I am using the Database Like - ELOG format and on the list page, the the last two columns (on the right side) are, "Text" and "Attachments (the paperclip)".
Both of which I have deleted from the input page.
Is there anyway to remove them from the List page?
Thanks, Mike
|
You need:
Show text = 0
Enable Attachments = 0
to supress the text entry box and the attachment field.
Display search = ID, Type, Location, Status
to show only the attributs of interest in the list display (your attributes could be different)
Summary lines = 0
to supress the text in the list display. At the moment, this still shows the paperclip colum, but I want to fix this in the next version.
|
66343
|
Mon May 4 11:50:30 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.5-2172 | Re: Using preset text files |
soren poulsen wrote: |
Hi,
I am trying the Preset text option from the documentation: like:
Attributes = Author, Type
Options Type = Network check{1}, System check{2}
{1} Preset text = network.txt
{2} Preset text = system.txt
I have two questions:
1. Where are the preset text files searched from ? I guess I could put them in the logbook (and specify a relative path like in this example) but it appeared only to work when I specifiy an abcolute path. That is even better in my case.
2. How do I specify line feeds in the file ? I tried Linux and Windows new line characters - but I always end up with just one line in my e-log. I would really like a multi-line form.
Soren
|
Without path, the file must reside in the "scripts" subdirectory.
For the multi-line form, it depends how you want to format your elog entry. If you format in "plain", the simple line breaks are sufficient. If you format in HTML, your preset file must be in HTML as well, so a line break has to be a <br> tag. If you format in ELCode, a simple line break again would be ok. |
66347
|
Wed May 6 15:30:24 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.7.6 | Re: Office 2007 file attachments download as zip due to mime config |
Rich Sterling wrote: |
Are there any plans to add the new mime extensions to the elogd.c source? (Instead of forcing users to use FireFox or Right click, save-as and rename?
|
Ok, I added the MIME extensions in ELOG Rev. 2196. The forum runs already the updated version, so can you try with the demo attachments from your entry? |
66348
|
Wed May 6 15:35:44 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2185 | Re: Problem Naming Logbooks |
mike cianci wrote: |
I have a logbook named "Centaur" (instrument name) for a problem log on an instrument and a logbook named "CentaurNewLot" for
a logbook (Database Like - ELOG format) where we would log reagent lot number changes for that instrument.
The problem is that when I name the logbooks, like I have, it screws up the formatting (List page) of the second log book.
If I rename the second logbook something totally unrelated to the first logbook my originally intended formatting returns.
|
I tried to reproduce your problem but without success. In my case the "CentaurNewLot" looks fine:

so what is different in your case? Can you try with the simple example logbook from the distribution and the add one option after the other to see which one causes the trouble? |
66349
|
Wed May 6 15:38:10 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2130 | Re: Mirror Server Funktion |
Andreas Wilke wrote: |
Ich möchte meine "lokale" ELOG Installation mit einem Server in der Firma synchronisieren.
Dazu habe ich in der entfernten Firewall ein Portmapping auf den ELOG Server in der Firma eingerichtet.
Wenn ich von meiner "lokalen" Maschine im Browser http://meinedomain.dyndns.xx:PORT aufrufe, kann ich auf den ELOG Server zugreifen.
Ich habe in meiner "lokalen" Installation in der Section [global] den Mirror-Server = http://meinedomain.dyndns.xx:PORT angeben.
Beim Synchornisieren bekomme ich jedoch den Hinweis "Fehler beim Zugriff auf entfertes Logbuch".......
|
Please let's stick to English. Let me try to understand your configuration. You have one elog server running and want to synchronize with itself? That does not work of course, synchronizing is done between two servers (normally on different computers). |
66350
|
Wed May 6 15:56:10 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.6-2191 | Re: "Forgot Password?" link not working? |
Mike wrote: |
I have my site running under apache. I don't have a /elog/ directory.
for example most would do http://www.example.com/elog/ to visit elog
but my site loads at http://www.example.com/
The site is private so it's password protected. Everything works fine except
if I click the "Forgot Password" link it does nothing.
but if I go to one of the log books...
http://www.example.com/open/
The forgot password link works.
Is there anyway to fix this? I have nothing else running on the server, it's dedicated to only ELOG.
That's why I don't want to have it running under /elog/ in the url.
|
Thanks for reporting this bug, I fixed it in revision 2197 which you can load from the SVN server. |
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. |
|