ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
65733
|
Mon Feb 11 22:24:37 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Windows | V2.7.2 | Re: Data Export:: Date Problem |
Richard Ecclestone wrote: |
Hi
Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,
the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.
This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.
|
What about exporting record separated by a semicolong ";" ? |
65734
|
Mon Feb 11 22:33:37 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Windows | V2.7.2 | Re: Data Export:: Date Problem |
Stefan Ritt wrote: |
Richard Ecclestone wrote: |
Hi
Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,
the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.
This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.
|
What about exporting record separated by a semicolong ";" ?
|
I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string. |
65735
|
Tue Feb 12 08:54:48 2008 |
| Richard Ecclestone | richard.ecclestone@cern.ch | Bug report | Linux | Windows | V2.7.2 | Re: Data Export:: Date Problem |
Stefan Ritt wrote: |
Stefan Ritt wrote: |
Richard Ecclestone wrote: |
Hi
Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,
the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.
This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.
|
What about exporting record separated by a semicolong ";" ?
|
I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string.
|
Hi Stefan
Thanks for the quick reply.
We seem to be running 2012 - Which may explain the problem - I will see with our system administrator why we are not running 2040. By the way I also had this problem when running the windows version.
Cheers.. Richard |
65736
|
Tue Feb 12 10:52:17 2008 |
| Richard Ecclestone | richard.ecclestone@cern.ch | Bug report | Linux | Windows | V2.7.2 | Re: Data Export:: Date Problem |
Richard Ecclestone wrote: |
Stefan Ritt wrote: |
Stefan Ritt wrote: |
Richard Ecclestone wrote: |
Hi
Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,
the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.
This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.
|
What about exporting record separated by a semicolong ";" ?
|
I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string.
|
Hi Stefan
Thanks for the quick reply.
We seem to be running 2012 - Which may explain the problem - I will see with our system administrator why we are not running 2040. By the way I also had this problem when running the windows version.
Cheers.. Richard
|
Hi Stefan
Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?
Where do we get version 2041 ?
Cheers, Richard
|
65737
|
Tue Feb 12 11:42:01 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Windows | V2.7.2 | Re: Data Export:: Date Problem |
Richard Ecclestone wrote: |
Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?
Where do we get version 2041 ?
|
The bleeding edge version you get always from our SVN server, but you have to recompile it yourself. For your convenience, I just made you a version 2.7.2-3 containing the latest source code. |
65738
|
Tue Feb 12 20:40:53 2008 |
| Richard Ecclestone | richard.ecclestone@cern.ch | Bug report | Linux | Windows | V2.7.2 | Re: Data Export:: Date Problem |
Stefan Ritt wrote: |
Richard Ecclestone wrote: |
Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?
Where do we get version 2041 ?
|
The bleeding edge version you get always from our SVN server, but you have to recompile it yourself. For your convenience, I just made you a version 2.7.2-3 containing the latest source code.
|
Thanks Stefan
Everything works now. |
67523
|
Mon Jun 3 15:53:22 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.2 | Re: 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 |
67527
|
Tue Jun 4 13:26:02 2013 |
| Martin Rongen | martin.rongen@rwth-aachen.de | Question | Linux | 2.9.2 | Re: 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 :) |