| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
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 |
|
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 |
|
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. |
|
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. |
|
1543
|
Thu Dec 8 10:32:37 2005 |
 | Bertram Metz | bmetz@sbs.com | Bug report | Linux | V2.6.0-bet | Attachments in duplicated entries | Hi,
the duplicate command duplicates the entry text itself, but it does not duplicate attachments.
If attachments in a duplicated entry are deleted, the original attachment files are deleted as well and cannot be accessed anymore within the original entry.
My suggestion is to copy the attached files too and to use file names of the copies in the duplicated entry.
Kind regards,
Bertram |
|
1546
|
Tue Dec 13 10:51:13 2005 |
 | Yoshio Imai | | Request | Linux | 2.6.0beta5 | Logbook aliases | Hi!
Is it possible to implement aliases for logbooks? We would like to use a new logbook for every beamtime, but many services need to read/write to the respective current beamtime logbook. It would therefore be nice to have logbook "aliases", so that e.g. a "virtual" logbook beam could be defined to be an alias/redirection to the current beamtime logbook, and all services could refer to that one instead of having to be reconfigured for each beamtime.
This could also help to make sure everyone on shift writes the entries to the correct logbook ... 
Yoshio Imai |
|
1547
|
Tue Dec 13 20:34:39 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.0beta5 | Re: Logbook aliases |
| Yoshio Imai wrote: | Is it possible to implement aliases for logbooks? We would like to use a new logbook for every beamtime, but many services need to read/write to the respective current beamtime logbook. It would therefore be nice to have logbook "aliases", so that e.g. a "virtual" logbook beam could be defined to be an alias/redirection to the current beamtime logbook, and all services could refer to that one instead of having to be reconfigured for each beamtime.
This could also help to make sure everyone on shift writes the entries to the correct logbook ...
|
You can do that already with the current version: At the end of a beamtime, create a new logbook, take the current logbook as a template, to make sure it has the same settings. Then move all entries from the current logbook to the new beamtime logbook, either with
- the "move to" command from the menu (which you first have to enable. While this works fine for individual entries, I never tried this with a whole logbook (click on "all", then "select all", then move to). So better try this first on a backup
- moving the logbook entries on the file level. Go to the elog root, then enter "mv logbooks/<current>/* logbooks/<beamtime>/ where <current> is your current (online) logbook and <beamtime> is the new one you just created. You have to restart elogd so that it realizes the moved files
After that, your current logbook is empty again and ready for the new beamtime  . |
|
1548
|
Wed Dec 14 11:40:54 2005 |
 | Yoshio Imai | | Request | Linux | 2.6.0beta5 | Re: Logbook aliases | Ok, we will try this.
In our case, the "symlink"-type logbook might have been nice because of our daily backup routines. If we move the data of the old logbook to the newly created one, the backup process would first need to upload all logbook data to the backup server under the new directory name and then delete those under the old name.
In our case this is not so much of a problem, because the logbooks are small (100MB), but maybe you can add this to the wishlist if others request the same... (We could try to adjust the backup procedure, but I don't know how well this would work).
Anyway, thanks for the work!
P.S. What do you think about the idea of a "Go to page"-button for the single entry view? |
|