Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 287 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  66861   Tue Jul 27 15:48:19 2010 Reply Johan Schuringjohan.schuring@getronics.comQuestionAll2.7.5Re: Mail when elog entry is expired

Stefan Ritt wrote:

Johan Schuring wrote:

Hi,

 

Is it possible to set a timestamp on an elog entry say for about 5 days in the future, when it is expired and there are no modifications with the entry you will get a mail.

I cannot find it with search in this forum or is the guides.

It can be very handy when it is possible.

When it is not available, is it possible to make a feature request for it.

This is not possible at the moment. Sounds to me more like a calendar function. What you could do however is to define an attribute of type "datetime", which you can populate with the expiration date. Then you can do a search to look for entries which are past the expiration date. But you have to do that manually like once per day or so. 

Thank you for your reply and the tip.

People can allways use another app (mail) for this, it would be nice,nothing more.

 

 

 

  66863   Wed Jul 28 16:55:32 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7Re: What *exactly* do "clone" and "mirror" do?

David McKee wrote:

We have been hosting logbook far (geographically and in internet hops) from our experimental site. Recently we have (finally!) gotten reliable on-site internet, and would like to host the log book on-site.

I have a suspicion that some combination of the -C, -m, and -M flags will allow me to migrate the logbook automagically and with a minimum risk of trouble from concurrent operation on the logbook, and to maintain the existing version as a mirror of the new official on-site version. But documentation is not being very helpful. Can someone say a few more words about what these options do?

 


I've been experimenting as I compose this and have a suggestion for language that might be useful somewhere in the documentation:

In this context "to clone" means to copy the configuration file and all data files associated with a log book so that I can host an identical logbook on a new host (that is this is the command to migrate a logbook).  After cloning the two installation are identical, but no effort is made to keep them so: if you continue to run both copies post made to one will not be reflected in the other.

Is this correct?

I'm still not clear on what the -m and -M options do.

Yes this is correct. But actually you do not necessarily need that. If you want to migrate a logbook to another server, you can just copy over the elog directory containing the configuration file and the logbooks. That's it. Mirroring now means manually triggered or periodic synchronization between two servers to keep the logbooks in sync. Like if an entry is entered on one server, it gets copied over to the other server automatically. That works in both directions. The periodic mirroring can be done using the options "Mirror server" and "Mirror cron" in the configuration files. It can be manually triggered using the "-m" and "-M" flags. But I guess in your case it's enough to copy over the elog tree just once. 

  66865   Wed Jul 28 17:08:55 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.8Re: Subst variables and Execute

soren poulsen wrote:

There is sometimes a problem with substitutions like "Execute delete = echo $message id".

It seems the problem is that if you delete a logbook entry that is not created with the current logbook attributes, the substitution variables are replaced with the variable name, and not the variable value.

In this example, according to the log file it becomes SHELL "message id" instead of SHELL "234", if the logbook entry is 234.

Soren

I tried to reproduce it, but it always worked for me. So I need a step-by-step instruction from you on how to reproduce the problem, ideally starting from the demo logbook from the distribution. Only if I can reproduce the problem, I will be able to fix it. 

  66867   Wed Jul 28 17:21:31 2010 Question Bryan Moffitmoffit@jlab.orgQuestionLinux2.7.8-2278Disable forward/backward navigation keystrokes?

I wondered if there was a config line that enabled/disabled the forward and backward navigation keystrokes that were implemented in 2.7.0?

The current definitions (Control-PgUp/PgDown/Home/End) interfere with those keys I use to navigate between tabs in Firefox.  It'd be nice if they could either be turned off.. or redefined.

  66868   Wed Jul 28 17:26:17 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.8-2278Re: Disable forward/backward navigation keystrokes?

Bryan Moffit wrote:

I wondered if there was a config line that enabled/disabled the forward and backward navigation keystrokes that were implemented in 2.7.0?

The current definitions (Control-PgUp/PgDown/Home/End) interfere with those keys I use to navigate between tabs in Firefox.  It'd be nice if they could either be turned off.. or redefined.

They are defined in

<ELOG directory>\scripts\elcode.js

Just go to the browse(evt) function and redefine or remove them there. 

  66869   Wed Jul 28 17:32:15 2010 Reply Bryan Moffitmoffit@jlab.orgQuestionLinux2.7.8-2278Re: Disable forward/backward navigation keystrokes?

Stefan Ritt wrote:

Bryan Moffit wrote:

I wondered if there was a config line that enabled/disabled the forward and backward navigation keystrokes that were implemented in 2.7.0?

The current definitions (Control-PgUp/PgDown/Home/End) interfere with those keys I use to navigate between tabs in Firefox.  It'd be nice if they could either be turned off.. or redefined.

They are defined in

<ELOG directory>\scripts\elcode.js

Just go to the browse(evt) function and redefine or remove them there. 

 Got it to work as desired.

 

Thanks for your help and your quick response.

  66871   Thu Jul 29 13:45:47 2010 Reply soren poulsensoren.poulsen@cern.chQuestionLinux2.7.8Re: Subst variables and Execute

Stefan Ritt wrote:

soren poulsen wrote:

There is sometimes a problem with substitutions like "Execute delete = echo $message id".

It seems the problem is that if you delete a logbook entry that is not created with the current logbook attributes, the substitution variables are replaced with the variable name, and not the variable value.

In this example, according to the log file it becomes SHELL "message id" instead of SHELL "234", if the logbook entry is 234.

Soren

I tried to reproduce it, but it always worked for me. So I need a step-by-step instruction from you on how to reproduce the problem, ideally starting from the demo logbook from the distribution. Only if I can reproduce the problem, I will be able to fix it. 

 It is of course my job to reproduce it (and explain how-to).  Thanks for your consideration.

  66874   Wed Aug 4 23:52:08 2010 Question Kontantin Olchanskiolchansk@triumf.caQuestionLinux2.8.0elog keeps recreating preview .png files?

Hi, I rsync an elog database from CERN to TRIUMF every few months and I notice that rsync keeps copying preview files (xxx.png.png, xxx.gif.png, etc) from very old entries. I guess that elogd creates these files from scratch each time they are needed, overwriting any previously existing preview files. This creates extra rsync network traffic and rsync takes longer to complete. Is there any way to avoid this? K.O.

 

ELOG V3.1.5-3fb85fa6