| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1552
|
Thu Dec 15 15:33:04 2005 |
 | Alex H | alex@synergie-inf.com | Other | Windows | 2.6.0 | Bad date format. | Hi Stefan,
I have two loogbook who are using the Type Derniere image = Date parameter, but I obtain a big
number instead of a formated date.
On my logbook "liste" (Look on the first attachement elog.gif please to watch the problem.)
I obtain this problem.
Here is the part of the elogd.cfg file for logbook "Liste" :
[Liste]
Theme = Bubble
Comment = Liste des routeurs / firewall clients
Type Dernière image = Date
List display = Client, Nom machine, Type, Equipment, Emplacement, Nom_admin, Pwd_admin, Maint, Derniere image
Link display = Client, Nom machine, Type, Equipment, Emplacement, Maint, Derniere image
Attributes = Client, Nom machine, Equipment, Type, Emplacement, Nom_admin, Pwd_admin, Maint, Derniere image
Extendable options = Client, Equipment
Options Type = FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}
{1} Preset text = FWL1.txt
{2} Preset text = FWL2.txt
{3} Preset text = FWL4.txt
{4} Preset text = VPN1.txt
{5} Preset text = VPN2.txt
{6} Preset text =
Preset Author = $short_name
Options Maint = Oui, Non
Required Attributes = Client, Type, Equipment, Nom machine, Maint
Locked Attributes = Author
Page Title = ELOG - $Nom machine
Reverse sort = 0
Quick filter = Client, Type, Maint
Summary lines = 2
Entries per Page = 50
Case sensitive search = 1
On my logbook "Image Routeurs" (Look on the second attachement elog2.gif)
No Problem
Here is the part of the elogd.cfg file for logbook "Liste" :
[Image Routeurs]
Theme = Bubble
Comment = Image Routeurs
Type Derniere Image = Date
Attributes = Equipment ,Client, Derniere Image
List display = Equipment ,Client,Derniere Image
Preset Author = $short_name
Locked Attributes = Author
Page Title = ELOG - $Equipment
Sort Attributes = Equipment
Reverse sort = 0
Quick filter = Equipment, Client
Reverse sort = 1
Sort Attributes = Equipment
Summary lines = 1
Display mode = Summary
What is wrong with my configuration ?
Thanks for answer. |
|
1551
|
Thu Dec 15 13:08:35 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | All | 2.6.0 | New ELOG version 2.6.0 | Dear ELOG users,
I'm happy to announce the release of ELOG version 2.6.0. After a long period of beta testing, all functions are now sufficiently stable for a public release. The major new feature is the introduction of the ELCode tags. They are similar to the well known BBCode tags, and let you format an elog entry. It is now also possible to embed inline images in an elog entry  , which are even sent in email notifications.
So have fun,
Stefan |
|
1550
|
Wed Dec 14 15:45:29 2005 |
 | Yoshio Imai | | Request | Linux | 2.6.0beta5 | Re: Logbook aliases |
| Stefan Ritt wrote: | | If you click "List" on the single entry page, it takes you by default to the listing page. |
I also think this is the best way to do it.
BTW, now that everyone here got used to the current elog look&feel, I think we no longer need the conditional hiding of attributes (don't hit me...  ). I hope you didn't invest too much time in that already.
Thanks, and happy beamtime!
Yoshio |
|
1549
|
Wed Dec 14 11:48:37 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.0beta5 | Re: Logbook aliases |
| Yoshio Imai wrote: | | but maybe you can add this to the wishlist if others request the same... |
Ok, I will do that.
| Yoshio Imai wrote: | | P.S. What do you think about the idea of a "Go to page"-button for the single entry view? |
I plan to make it even better (when I get some time, we have beam time right now as well  ). If you click "List" on the single entry page, it takes you by default to the listing page. I guess that would be a feature of general interest. I just need some time to implement it... |
|
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? |
|
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  . |
|
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 |
|
1545
|
Mon Dec 12 15:17:39 2005 |
| Willem Koster | W.Koster@rc.rug.nl | Question | Other | ELOG V26b5 | duplicate & presets | I'm (mis)using elog as a database. I like the fact that I can have presets for fields, but I also like the fact
that I can make a duplicate of an entry. Now when I make a duplicate, all the fields get overwritten with the
preset-value. Is there a way to get the preset-values only on entering a NEW reord and NOT on a duplicate ?
I could take away the presets, most of them are "***" (literally) to be able to search for entries that do not
have a value, but I don't know how to search for empty fields.
PS: They wanted to do a CMDB in BMC-Magic (really expensive $$$-ware), but after about 1 afternoon (and about 6
prototypes) they went with elog since it was fast, cheap and already implemented (and filled with 200 entries
through a script using some old CSV list we had lying around) :-)
|
|