ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66342
|
Mon May 4 11:25:15 2009 |
| soren poulsen | soren.poulsen@cern.ch | Question | Linux | 2.7.5-2172 | Re: Using preset text files |
soren poulsen wrote: |
Hi,
I am trying the Preset text option from the documentation: like:
Attributes = Author, Type
Options Type = Network check{1}, System check{2}
{1} Preset text = network.txt
{2} Preset text = system.txt
I have two questions:
1. Where are the preset text files searched from ? I guess I could put them in the logbook (and specify a relative path like in this example) but it appeared only to work when I specifiy an abcolute path. That is even better in my case.
2. How do I specify line feeds in the file ? I tried Linux and Windows new line characters - but I always end up with just one line in my e-log. I would really like a multi-line form.
Soren
|
Dear Soren,
Just use HTML (and call the file network.html to remember).
|
66343
|
Mon May 4 11:50:30 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.5-2172 | Re: Using preset text files |
soren poulsen wrote: |
Hi,
I am trying the Preset text option from the documentation: like:
Attributes = Author, Type
Options Type = Network check{1}, System check{2}
{1} Preset text = network.txt
{2} Preset text = system.txt
I have two questions:
1. Where are the preset text files searched from ? I guess I could put them in the logbook (and specify a relative path like in this example) but it appeared only to work when I specifiy an abcolute path. That is even better in my case.
2. How do I specify line feeds in the file ? I tried Linux and Windows new line characters - but I always end up with just one line in my e-log. I would really like a multi-line form.
Soren
|
Without path, the file must reside in the "scripts" subdirectory.
For the multi-line form, it depends how you want to format your elog entry. If you format in "plain", the simple line breaks are sufficient. If you format in HTML, your preset file must be in HTML as well, so a line break has to be a <br> tag. If you format in ELCode, a simple line break again would be ok. |
66344
|
Mon May 4 18:06:01 2009 |
| soren poulsen | soren.poulsen@cern.ch | Question | Linux | 2.7.5-2172 | Re: Using preset text files |
Stefan Ritt wrote: |
soren poulsen wrote: |
Hi,
I am trying the Preset text option from the documentation: like:
Attributes = Author, Type
Options Type = Network check{1}, System check{2}
{1} Preset text = network.txt
{2} Preset text = system.txt
I have two questions:
1. Where are the preset text files searched from ? I guess I could put them in the logbook (and specify a relative path like in this example) but it appeared only to work when I specifiy an abcolute path. That is even better in my case.
2. How do I specify line feeds in the file ? I tried Linux and Windows new line characters - but I always end up with just one line in my e-log. I would really like a multi-line form.
Soren
|
Without path, the file must reside in the "scripts" subdirectory.
For the multi-line form, it depends how you want to format your elog entry. If you format in "plain", the simple line breaks are sufficient. If you format in HTML, your preset file must be in HTML as well, so a line break has to be a <br> tag. If you format in ELCode, a simple line break again would be ok.
|
Thanks for the hints on the "scripts" dir. For the formatting, that's clear. I started with the sample "network.txt" file from the doc and the default encoding (HTML), so that did (of course) not render correctly (before inserting a few tags).
Soren
|
545
|
Fri May 21 15:03:48 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.2 | Re: Using date and subst date |
> I'm trying capture any edit/modified entry with the following, Using the
> real date format instead of text string so that I could do a quick filter on it.
>
> Type modified = date
> Subst on Edit modified = $date
>
> Problem: It seem that the Subst on Edit always default to 1 Jan 1970 instead
> of current date on edit screen.
I fixed that problem, new version under
http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.328 |
546
|
Sat May 29 04:23:58 2004 |
| nait tauh | nait@no2bl.no-ip.com | Question | Linux | 2.5.2 | Re: Using date and subst date |
> I fixed that problem, new version under
> http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.328
Any binary build anywhere that I can pick? Thanks.
nait. |
548
|
Wed Jun 2 15:13:12 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.2 | Re: Using date and subst date |
>
> > I fixed that problem, new version under
> > http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.328
>
> Any binary build anywhere that I can pick? Thanks.
>
> nait.
http://midas.psi.ch/elog/download/windows/elogd-snapshot.exe
is for windows, for linux you have to recompile with
gcc -O -o elogd elogd.c
Best regards,
Stefan |
549
|
Thu Jun 3 17:15:56 2004 |
| nait tauh | nait@no2bl.no-ip.com | Question | Linux | 2.5.2 | Re: Using date and subst date |
> http://midas.psi.ch/elog/download/windows/elogd-snapshot.exe
>
> is for windows, for linux you have to recompile with
>
> gcc -O -o elogd elogd.c
>
> Best regards,
>
> Stefan
Hi Stefan,
I tried compile it in gentoo 1.4 GCC 3.3.3 without problem. However, it refuse
to run on ipcop box. The error message,
./elogd: /lib/libc.so.6: version `GLIBC_2.3' not found (required by ./elogd)
I guess the kernel and/or compiler version is not matching. Any simple way to
fix it? Thanks for your help?
nait. |
550
|
Thu Jun 3 17:28:07 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.2 | Re: Using date and subst date |
> > http://midas.psi.ch/elog/download/windows/elogd-snapshot.exe
> >
> > is for windows, for linux you have to recompile with
> >
> > gcc -O -o elogd elogd.c
> >
> > Best regards,
> >
> > Stefan
>
> Hi Stefan,
>
> I tried compile it in gentoo 1.4 GCC 3.3.3 without problem. However, it refuse
> to run on ipcop box. The error message,
> ./elogd: /lib/libc.so.6: version `GLIBC_2.3' not found (required by ./elogd)
>
> I guess the kernel and/or compiler version is not matching. Any simple way to
> fix it? Thanks for your help?
Looks like a weird Linux installation. Maybe try to link static:
gcc -O -static -o elogd elogd.c
executable will be much bigger, but maybe work... |