ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1346
|
Wed Jul 27 15:49:16 2005 |
| Juliana Peng | jpeng@yorku.ca | Request | Linux | V2.6.0 | Re: hide attributes when view the logbook |
Stefan Ritt wrote: |
In that case I would suggest two separate logbooks, for for SunOS and one for others. This way you can manage two separate sets of attributes. |
We don't want separate logbooks, sorry for the misleading. I was trying to put two request together.
1. We have several user using the logbook. Is there a way each one has his own "List Display". In our case the user also is an attribute(SysAdmin) in logbook:
Attributes = Name, SysAdmin, Manufacturer, Model, Serial Number, Description, ENV, Main Function, Location, Memory, CPU Speed, Num CPU, Owner, Contact Name, Contact Phone, Contact Email, Bought From, Bought Date, Maintenance, Network Drop,Console Drop
Options SysAdmin = user1{1}, user2{2}, user3{3}
so one way we can think of is using "{1} List Display = ...."
"{2} List Display = ...."
"{3} List Display = ...."
because most of the time the user is interested in his own machine. Maybe you have better suggestion.
2. We need to change elog.conf file to use or not use "List Display". Is there a way to control it through web? If this is not applicable. It's fine, we won't change the view frequently. |
1348
|
Wed Jul 27 16:31:33 2005 |
| Juliana Peng | jpeng@yorku.ca | Request | Linux | V2.6.0 | Re: hide attributes when view the logbook |
Stefan Ritt wrote: |
I understood you correctly. What I was trying to say is that what you currently request possible with the current version and will not be implemented soon. But you can partly obtain what you want by having two logbooks. Make one logbook which has fewer attributes, and which will receive all SunOS entries. Make another one with all the attributes. Although this will become separate logooks, you can "think" of them as one logbook with two different sections. There is even the trick of forcing the data directory to be the same (via the "data dir") option, so both logbooks will "look" at the same database. Make one logbook the "master" having all the attributes. That's where you enter your information. Them make one or more logbooks looking at the same data, but make them read-only. Each logbook can have a separate set of attributes, access rights etc, but all of them show the same data.
I know this is not the perfect solution, but at least something which can be done already now. |
Thank you so much. We'll try it. Waiting for your next version. |
68156
|
Mon Oct 26 15:20:44 2015 |
| Julian Brower | julian.brower@stfc.ac.uk | Question | Windows | latest | Please advise on how to set up selective email notification on logbooks | Please advise on how to set up selective email notification on logbooks; We want to send an email to specific people when an event that involves them is entered?
At the moment, we currently get an email entry for every new logbook entry. Thanks
|
68157
|
Mon Oct 26 15:24:44 2015 |
| Julian Brower | julian.brower@stfc.ac.uk | Question | Windows | Latest | How can we calculate and display the difference between two time entries on a log entry | See drawing below: We have a beam on and a beam off time. We want to fill in the lost time automaticaaly. Please can you help? Julian
|
68159
|
Tue Oct 27 09:26:56 2015 |
| Julian Brower | julian.brower@stfc.ac.uk | Question | Windows | Latest | Re: How can we calculate and display the difference between two time entries on a log entry | Stefan, I am not an expert in this field so I wondered how one goes about finding someone to write this and how one amends the soruce code? Is that allowed? Is it a feature than may be of use for other users? Julian
Stefan Ritt wrote: |
Unfortunately elog cannot do calculations based on certain fields. You could however add some Javascript code (via "Bottom text = ..." for example), which does that. But that requires JavaScript knowledge to do so.
Julian Brower wrote: |
See drawing below: We have a beam on and a beam off time. We want to fill in the lost time automaticaaly. Please can you help? Julian
|
|
|
68166
|
Tue Oct 27 14:58:20 2015 |
| Julian Brower | julian.brower@stfc.ac.uk | Question | Windows | latest | Re: Please advise on how to set up selective email notification on logbooks | Thanks Andreas, I will read that section. Julian
Andreas Luedeke wrote: |
Hi Julian,
there is a whole chapter in the documentation about that: https://midas.psi.ch/elog/config.html#email
If I have to send email, e.g. for Controls issues entered in the operation logbook, I do send the email to a specific mailman mailing list for that group.
It is cumbersome to manage email groups in the logbook configuration - in particular if the same lists exists in different logbooks. I only refer to the mailing list then in ELOG, and the groups can manage their lists themself.
I do maintain about 30 logbooks and there are about 10 groups at my institutes that desire email notifications for ELOG entries related to the systems they manage.
Cheers
Andreas
Julian Brower wrote: |
Please advise on how to set up selective email notification on logbooks; We want to send an email to specific people when an event that involves them is entered?
At the moment, we currently get an email entry for every new logbook entry. Thanks
|
|
|
67098
|
Tue Aug 2 13:55:06 2011 |
| Juergen Lupke | juergen.lupke@computacenter.com | Question | Linux | V2.9.0-241 | present Text | I have define a MOption BACKUP = Server, Switch, Router any now i link to use the Status of the Backup Option to display diffrent html file in the Text field, i the a posible way to do this ?
sample:
MOption BACKUP = Server, Switch, Router
{Server&Switch&Router} Present Text = file1
{Server&Switch} Present Text = file2 |
68270
|
Fri Feb 26 17:35:54 2016 |
| Juergen Diefenbach | diefenba@uni-mainz.de | Bug report | Linux | 3.1.1 | Execute new|edit doesn't seem to work | I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
When a new entry is created a shell script should be executed (certain attributes of the logbook entry should be passed as arguments to it). The script will then automatically stage all changes and create an appropriate git commit message. For a "new" entry in the logbook the commit message is a bit more verbose. When editing or deleting a message only a short commit message like "Edit message 25" should be created. Therefore I really need to distinguish between "new", "edit", and "delete".
However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the one specified by "Execute edit=" is executed. Most of the time it doesn't work as expected. 
What I did so far to understand what goes wrong is I looked into elogd.c and found invoid submit_elog(LOGBOOK * lbs) that bedit is sometimes true and sometimes false, when creating a new entry, although it should be false then (right?).
This is why elogd then sometimes retrieves the wrong shell command from getcfg(lbs->name, "Execute edit"...) instead of getcfg(lbs->name, "Execute new"...) around line 23610 (not exact due to some eprintf()s inserted here and there to look at bedit and so on).
When deleting an entry, everything works fine: the shell command defined via "Execute delete=" is run, but this happens somewhere else in the code so it's not a surprise.
Do you have an idea how to fix this or can you point me in some direction to further track it down? Thank you! |
|