Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 518 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  67516   Wed May 29 14:57:23 2013 Reply Andreas Luedekeandreas.luedeke@psi.chInfoLinux2.8-2350Re: hyperlink other elog posts

Remington Tyler Thornton wrote:

I am on an experiment that used ELOG for all documentation and meeting notes. In our meeting notes we link to elog posts that had been discussed during the meeting. We had done this by hyperlinking the URL to the entry. Recently we had to move our logbook to another machine and so none of our hyperlinks work since the URLs have changed. I noticed that when one creates a new entry in the subject they can reference another post. Is there a way to link another elog in the body of the elog by using its logbook name and id number without having to use a URL?

Thanks in advance

This is one of the rare cases where it helps to read the manual: https://midas.psi.ch/elog/userguide.html#add (You may need to upgrade to elog 2.9)

If you want to replace the old URLs with the new ones, you can edit the logbook files with the entries. The attached script allows you to do so easily. But be careful, try it on a copy of your data first.

 
Detect language » English
 
 
Detect language » English
 
Using:
regreplace "<old-url>" "<new-url>" *a.log
 
I hope this helps.
Andreas
Attachment 1: regreplace
#!/bin/bash
if [ $# -lt 3 ]
then
	echo "using: $0 <search-for> <replace-with> <file-list>"
	exit
fi
if [ "$1" = "-f" ]
then 
	flag="-f"
	shift 1
else
	flag="-i"
fi
search="$(echo "$1"|awk '{gsub("\\","\\\\");gsub("/","\\/");print $0}')"
replace="$(echo "$2"|awk '{gsub("\\","\\\\");gsub("[$]","\\$");gsub("/","\\/");print $0}')"
shift 2
echo "replace \"$search\" with \"$replace\" in the files "
bold=`tput smso`
offbold=`tput rmso`
for file in $(grep -l "$search" "$@")
do
	tmp=/tmp/regreplace_$(basename $file)
	sed "s/${search}/${replace}/g" $file >$tmp
	
	echo "${bold}diffs of $file$offbold ('<' = before, '>' = after)"
	diff $file $tmp
	cp $flag $tmp $file
        rm -f $tmp
done
  67521   Mon Jun 3 15:44:46 2013 Entry Martin Rongenmartin.rongen@rwth-aachen.deQuestionLinux2.9.2Daemonizing vs. shell execution

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

  67522   Mon Jun 3 15:49:33 2013 Reply Martin Rongenmartin.rongen@rwth-aachen.deInfoLinux2.6.0Re: "full" only changes color

Kees Bol wrote:
Hi,
I have the strange problem that when changing to "full"-diplaymode the output looks the same as with "summary", only the color is different. The texts don't appear.
Any idea what can cause this behaviour?

thanks
Kees Bol



I now have the same problem in 2.9.2. Attached please find the elogd.cfg

Best regards
Martin
Attachment 1: elogd.cfg
[global]
port = 8080
Logbook Tabs=0 ;this is the only logbook here

[EDM beamtime logbook]
Theme = default
Title image URL = http://lx3b58:8888/EDM+beamtime+logbook/
Password file = passwd
Self register = 0
Admin user = jedi_admin

Menu commands = New, Reply, Find, Login, Config
Guest menu commands = New, Reply, Find, Login
List Menu commands = New, Find, Help, Logout, Config
Guest List Menu commands = New, Find, Last Day, Help, Login

Attributes = entry type, run number , Start, Stop,  run type, operators, shift, COSY state, DAQ state, comments
List display =Date, entry type, comments, run number, run type, operators, shift, COSY state, DAQ state
Guest List display =Date, entry type, comments, run number, run type, operators, shift, COSY state, DAQ state

Options entry type = run{1}, comment{2}, shift summary{3}, reply{4}
Preset entry type = run
Preset on reply Entry type = reply
Subst on reply comments = Re: $comments
{1,2,3} Options entry type = run{1}, comment{2}, shift summary{3}
{4} Options entry type =  reply
	
Cell Style entry type run = background-color:#b9ca67
Cell Style entry type comment = background-color:#bd9c73
Cell Style entry type shift summary = background-color:#d6b6e6
Cell Style entry type reply = background-color:#5cb8ff

Required Attributes = entry type

{1} Show Attributes Edit= entry type, run number , Start, Stop,  run type, operators, shift, COSY state, DAQ state, comments
{1} Required Attributes = operators, shift, run number, run type, COSY state, DAQ state

{2} Show Attributes Edit= entry type, operators, shift, COSY state, DAQ state, comments
{2} Required Attributes = operators, shift, COSY state, DAQ state

{3} Show Attributes Edit= entry type, operators, shift, COSY state, DAQ state, comments
{3} Required Attributes = operators, shift, COSY state, DAQ state

{4} Show Attributes Edit= entry type, operators, comments, run number, run type
{4} Required Attributes = operators

Options Shift = Morning, Day, Night
Options run type = Test entry, ED SCT
Options COSY state = Problem, Maintenance, Running
Options DAQ state = OK, Faulty

Cell Style COSY state Problem = background-color:red
Cell Style COSY state Maintenance =  background-color:yellow 
Cell Style COSY state Running = background-color:green
Cell Style DAQ state OK = background-color:green
Cell Style DAQ state Faulty = background-color:red

Extendable options = run type

Fixed Attributes Edit = run type, COSY state, DAQ state, entry type, run number, Start, Stop, shift 
Fixed Attributes Reply = entry type, run type, COSY state, DAQ state, entry type, run number, Start, Stop, shift, comments

Page Title = EDM beamtime logbook
Reverse sort = 1
Quick filter = run number

{1} Preset run number = $shell(bash preset_run.sh 2>/dev/null)
;looks up last run number in logbook folder and increments


;Type run number = numeric
Type Start  = datetime
Type Stop = datetime
{1} Preset Start =  $utcdate
{1} Preset Stop =   $utcdate

Thumbnail size=500

Summary lines = 0 ;so it doesnt appear on front page

Search all logbooks = 0

Default encoding = 2 ; html-necessary for latex
Allowed encoding = 4 ; only html allowed

Time format = %A, %B %d, %Y, %H:%M 
{1} Execute new = bash append_root.sh $run number
 ; adds link to root-file

RSS Title = run $comment, posted by $operators on $entry time

; No Email notification
Suppress Email to users = 1

  67523   Mon Jun 3 15:53:22 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2Re: Daemonizing vs. shell execution

Martin Rongen wrote:

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

Usually the problem comes from the fact that a daemon runs from the root directory ('/') by definition. I might not find your scripts if they are not in the path. Try to call them explicitly with the ful path like "/usr/local/elog/script.sh".

/Stefan 

  67524   Mon Jun 3 20:02:38 2013 Question David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.9.2-2475Sorting by numeric attribute (not entry ID).
By default, elog enties are sorted by their ID number.  When viewing a logbook in Full or Summary, they are
shown in strict order of ID.  In Threaded, entries are shown in strict order of ID for the latest entry of each
thread, and then previous entries (in reply to) back from the latest one.  

In collapsed mode, it is only the starting entry of each thread is shown (or the latest one if "collapse to
last" chosen, but that's a detail).

I have a couple of logbooks where I'd like the default sorting to be by another numeric attribute that I enter. 

Now this works fine in Full or Summary mode.  In threaded mode (e.g. default for this forum, where every entry
is shown but are grouped by thread), it works in as much as all the entres are there and in order, but it
doesn't quite look the same as when sorting by ID - the replies are not each offset further right beneath the
entry it is in reply to, but all just slightly offset to the first entry.  

If you try to [completely] collapse the threaded mode to just one line per threaded topic - it doesn't.  Looks
(almost) the same as threaded.

I was hoping to get the list of entries collapsed to one line per thread, in order of the numeric attribute, but
I cannot seem to get this to happen.   Have I missed something here?  Or is it possible at all?
  67525   Tue Jun 4 12:03:18 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2-2475Re: Sorting by numeric attribute (not entry ID).
> By default, elog enties are sorted by their ID number.  When viewing a logbook in Full or Summary, they are
> shown in strict order of ID.  In Threaded, entries are shown in strict order of ID for the latest entry of each
> thread, and then previous entries (in reply to) back from the latest one.  
> 
> In collapsed mode, it is only the starting entry of each thread is shown (or the latest one if "collapse to
> last" chosen, but that's a detail).
> 
> I have a couple of logbooks where I'd like the default sorting to be by another numeric attribute that I enter. 
> 
> Now this works fine in Full or Summary mode.  In threaded mode (e.g. default for this forum, where every entry
> is shown but are grouped by thread), it works in as much as all the entres are there and in order, but it
> doesn't quite look the same as when sorting by ID - the replies are not each offset further right beneath the
> entry it is in reply to, but all just slightly offset to the first entry.  
> 
> If you try to [completely] collapse the threaded mode to just one line per threaded topic - it doesn't.  Looks
> (almost) the same as threaded.
> 
> I was hoping to get the list of entries collapsed to one line per thread, in order of the numeric attribute, but
> I cannot seem to get this to happen.   Have I missed something here?  Or is it possible at all?

This is not possible at the moment, but I will add it to the wish list.
  67527   Tue Jun 4 13:26:02 2013 Reply Martin Rongenmartin.rongen@rwth-aachen.deQuestionLinux2.9.2Re: Daemonizing vs. shell execution

Stefan Ritt wrote:

Martin Rongen wrote:

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

Usually the problem comes from the fact that a daemon runs from the root directory ('/') by definition. I might not find your scripts if they are not in the path. Try to call them explicitly with the ful path like "/usr/local/elog/script.sh".

/Stefan 

 I didn't know that. Thanks for the quick response. I have it working now :)

  67528   Tue Jun 4 15:00:23 2013 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.9.2-2475Re: Sorting by numeric attribute (not entry ID).
> > By default, elog enties are sorted by their ID number.  When viewing a logbook in Full or Summary, they are
> > shown in strict order of ID.  In Threaded, entries are shown in strict order of ID for the latest entry of each
> > thread, and then previous entries (in reply to) back from the latest one.  
> > 
> > In collapsed mode, it is only the starting entry of each thread is shown (or the latest one if "collapse to
> > last" chosen, but that's a detail).
> > 
> > I have a couple of logbooks where I'd like the default sorting to be by another numeric attribute that I enter. 
> > 
> > Now this works fine in Full or Summary mode.  In threaded mode (e.g. default for this forum, where every entry
> > is shown but are grouped by thread), it works in as much as all the entres are there and in order, but it
> > doesn't quite look the same as when sorting by ID - the replies are not each offset further right beneath the
> > entry it is in reply to, but all just slightly offset to the first entry.  
> > 
> > If you try to [completely] collapse the threaded mode to just one line per threaded topic - it doesn't.  Looks
> > (almost) the same as threaded.
> > 
> > I was hoping to get the list of entries collapsed to one line per thread, in order of the numeric attribute, but
> > I cannot seem to get this to happen.   Have I missed something here?  Or is it possible at all?
> 
> This is not possible at the moment, but I will add it to the wish list.

OK, Thanks Stefan.
ELOG V3.1.5-3fb85fa6