ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66897
|
Mon Sep 13 09:23:29 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.8.-2312 | Re: How to setup elogd as windows service with shell execution? |
Robert Heine wrote: |
Dear colleagues,
I am trying to use the elogd as a service with activated shell-execution. Invoking 'elogd -x' on the command line works fine, as well as 'elogd -install'. The option 'elogd -x -install' does not seem to be implemented, so I followed two ways to get this to work:
1) creating my own service with instsrv/srvany and registry editing: starting 'elogd -x' does not work (error 1053), the -D option has to be added, to start the service without time out. But then shell execution seems to be not working, because no input to the elog is generated, but also no message saying shell execution was not enabled!
2) using 'elogd -install' and modifying the registry entry by adding the -x option to the command line in the 'HKLM\System\CurrentControlSet\Services\elogd\ImagePath': This enables shell execution, but instead of piping the output to the logbook, some DOS boxes pop up executing the shell command and terminate. No entries are generated.
Has anyone an idea?
|
I could never get shell execution work when elogd is started as a service. This has probably to do with system permissions or so under Windows. If anybody has a clue, please let me know. Under Linux this works nicely, but this is probably not an option for you... |
67514
|
Tue May 28 19:01:42 2013 |
| Remington Tyler Thornton | rtthornt@indiana.edu | Info | Linux | 2.8-2350 | hyperlink other elog posts |
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 |
67516
|
Wed May 29 14:57:23 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | 2.8-2350 | Re: 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
|
66879
|
Thu Aug 19 15:26:35 2010 |
| Mike Zuber | mdz0739@yahoo.com | Bug report | Windows | 2.8 | Elogd service crashes on "reply" with percent character in subject line |
My logbook kept crashing whenever I tried to reply to an existing entry. I found that the percent sign "%", when used in the subject line, will crash the elogd service when you try to reply to the entry. This appears to only happen with windows installations. I tested this on your Linux logbook and it didn't crash.
Here is the message taken from the Windows event viewer after the crash:
An unhandled win32 exception occurred in elogd.exe [5224].
Thank you for Elog, you have done a good job with it. It is a great logbook.
Mike |
66907
|
Wed Sep 15 22:40:52 2010 |
| Mike Zuber | mdz0739@yahoo.com | Question | Windows | 2.8 | Action after message submission |
Is it possible to automatically go back to the list view in summary mode after submitting a new message instead of displaying the new message?
I know it's possible to display a page from a file after submitting a new message by using "Submit Page = <file>".
It would be nice to be able to use a command like "Submit Page = <command>" where I could insert "?cmd=Back" as in the "Start page" command.
Thanks,
Mike |
66908
|
Fri Sep 17 00:59:16 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.8 | Re: Action after message submission |
Mike Zuber wrote: |
Is it possible to automatically go back to the list view in summary mode after submitting a new message instead of displaying the new message?
I know it's possible to display a page from a file after submitting a new message by using "Submit Page = <file>".
It would be nice to be able to use a command like "Submit Page = <command>" where I could insert "?cmd=Back" as in the "Start page" command.
Thanks,
Mike
|
I just implemented a new flag "List after submit = 1" which does exactly this. It brings you to the summary page after the submission of a new entry. I needed the function myself. The change is SVN revision 2327 and will be contained in the next release. |
66914
|
Wed Sep 22 14:37:10 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.8 | Re: Elogd service crashes on "reply" with percent character in subject line |
Mike Zuber wrote: |
My logbook kept crashing whenever I tried to reply to an existing entry. I found that the percent sign "%", when used in the subject line, will crash the elogd service when you try to reply to the entry. This appears to only happen with windows installations. I tested this on your Linux logbook and it didn't crash.
Here is the message taken from the Windows event viewer after the crash:
An unhandled win32 exception occurred in elogd.exe [5224].
Thank you for Elog, you have done a good job with it. It is a great logbook.
Mike
|
I could not reproduce your problem. I tried the very simple config file:
[Demo]
Attributes = Author, Subject
and the problem did not occur (see attachment). Can you try the most recent version (elog280-4.exe) with this simple configuration. Maybe you have a more complicated configuration which causes the problem. In that case please send it to me, so that I can reproduce the problem. |
Attachment 1: Capture.png
|
|
66919
|
Thu Oct 14 16:43:05 2010 |
| Mike Zuber | mdz0739@yahoo.com | Question | Windows | 2.8 | Re: Action after message submission |
Stefan Ritt wrote: |
Mike Zuber wrote: |
Is it possible to automatically go back to the list view in summary mode after submitting a new message instead of displaying the new message?
I know it's possible to display a page from a file after submitting a new message by using "Submit Page = <file>".
It would be nice to be able to use a command like "Submit Page = <command>" where I could insert "?cmd=Back" as in the "Start page" command.
Thanks,
Mike
|
I just implemented a new flag "List after submit = 1" which does exactly this. It brings you to the summary page after the submission of a new entry. I needed the function myself. The change is SVN revision 2327 and will be contained in the next release.
|
Thank you very much! I appreciate it. |