ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1541
|
Wed Dec 7 02:32:00 2005 |
| Jesse Wodin | jwodin@stanford.edu | Question | Linux | 2.6.0 | Re: Upgrade from 2.3.8 to 2.6.0 logbook problem |
Thanks, you were right, it was just a permissions problem on the logbooks, which I had copied over as root.
j. |
1540
|
Mon Dec 5 17:11:33 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0 | Re: Upgrade from 2.3.8 to 2.6.0 logbook problem |
Jesse Wodin wrote: | Hi, I'd like to upgrade from an old version of elog 2.3.8 to 2.6.0. I installed the new version, and it runs fine, but it doesn't seem to see my old logbooks (the path in the conf file is correct). Do I have to upgrade my logbooks somehow? |
No. The last change in the logbook format was for version 2.0.0. So something else must be wrong. Just creat one entry with your new elog, and see where it's created on the hard disk. Put your old logbooks there. If you start elogd manually with the "-v" flag, you will see it indexing all logbooks. Check that you see all your entries there. |
1539
|
Sat Dec 3 23:32:13 2005 |
| Jesse Wodin | jwodin@stanford.edu | Question | Linux | 2.6.0 | Upgrade from 2.3.8 to 2.6.0 logbook problem |
Hi, I'd like to upgrade from an old version of elog 2.3.8 to 2.6.0. I installed the new version, and it runs fine, but it doesn't seem to see my old logbooks (the path in the conf file is correct). Do I have to upgrade my logbooks somehow?
THanks!
Jesse |
1538
|
Fri Dec 2 12:27:47 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.5.6.1 | Re: Upgrading from ELOG V2.5.6-1 to ELOG V2.5.9 steps |
Rob de Bruin wrote: | We whant to upgrade to the latest version, can i just install the latest version over my older version??
I wil backup etc. offcourse. |
Yes. The 2.6.0-beta1,2,3,4 have some problems, but the latest beta5 is pretty stable.
Rob de Bruin wrote: | Are there things i'll have to be alert to? |
Usually only new options get added, and I keep the old ones, so there should not be any problem, although I do not record carefully what changes between any arbitray versions, so just read the changelogs
Rob de Bruin wrote: | Can someone give me a link to a document? |
The changelog is located at http://midas.psi.ch/elog/download/ChangeLog
I have not put in the new stuff from 2.6.0, because it's still in beta.
- Stefan |
1537
|
Fri Dec 2 11:46:11 2005 |
| Rob de Bruin | rdbruin@zernike.nl | Request | Linux | 2.5.6.1 | Upgrading from ELOG V2.5.6-1 to ELOG V2.5.9 steps |
Hello,
Were still running (stable) Elog version V2.5.6-1.
We whant to upgrade to the latest version, can i just install the latest version over my older version??
I wil backup etc. offcourse.
Are there things i'll have to be alert to?
Can someone give me a link to a document?
Best regards Rob de Bruin |
1536
|
Fri Nov 25 14:05:08 2005 |
| Yoshio Imai | | Bug report | Linux | 2.6.0beta5 | Re: "Logkook dir" in top group [global] section ineffective |
OK, I found the note about "Logbook dir" in Stephen Wood's entry (http://midas.psi.ch/elogs/Forum/1101)  |
1535
|
Thu Nov 24 20:08:00 2005 |
| Yoshio Imai | | Bug report | Linux | 2.6.0beta5 | "Logkook dir" in top group [global] section ineffective |
Hi, it's me again!
I have found one possible bug. We have declared top groups for our logbooks; one for administration and one for the shift logbooks. In the [global]-section there is a "Logbook dir"-statement of the form
[global]
Top group Admin = <...>
Top group Shiftlogs = beamtime1,beamtime2,...
Logbook dir = /data/logbooks
Now, in the [global Shiftlogs] section there is another "Logbook dir"-statement to have all associated logbooks in one tree:
[global Shiftlogs]
Logbook dir = /data/logbooks/shift-logbooks
[beamtime1]
Subdir = beamtime1
The problem is, that the manually created subdirectories /data/logbooks/shift-logbooks/beamtimeN are ignored, and the elogd creates new "Subdir"-directories /data/logbooks/beamtimeN (as if the "Logbook dir" statement in the top group [global] section were ineffective). Is this a bug or configuration error from our side?
There are also one question/request (you see that we use the elog extensively now ):
When searching for a particular event in our shift log using the "Find" function, it would often be useful not to go to the single entry, but to the page where that entry resides. This way we can see the whole context of the event. When clicking onto an entry in the "Find" result page, this takes us of course to the single entry, but could you add a function to go to the page instead. Alternatively, is it possible to include a button "Go to page" in the single entry view (it need not even be exactly +/-N entries around, the usual page partition would do)?
Thanks in advance.
Yoshio |
1534
|
Thu Nov 24 08:27:01 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0-beta | Re: Email format flags |
Elaine Cristina Franchini dos Anjos wrote: | I've been tried to format our email notification messages
like this forum, but I couldn't.
Every email notification is sent in plain text although I've tried
all options listed in documentation about Email Format flags. 
What is the Email Format flag that I need to use ?
Is there something else that I have to configure ? ?) |
The email notification is under revision right now, that's why 2.6.0 is still in beta. It will change again before the final release. I want to make a multipart/alternative encoding, where plain text and HTML are sent in the same email, and the user can select on the email client which part to view.
In the 2.6.0-beta5, you can select the eamil format with
Email encoding = 4
which then produces the same notifications as the forum. |