ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1080
|
Tue Apr 12 16:07:12 2005 |
| Steve Woughter | woughter@yahoo.com | Question | Windows | | Conditional conditions? |
Can conditional attributes be assigned as conditions?
Arbitraty Example:
Attributes = Operating system, Version, Name
Options Opperating system = Linux {1}, Windows {2}
{1} Options Version = 2.2 {a}, 2.4 {b}, 2.6 {c}
{2} Options Version = ME {d}, 2k {e}, NT {f}, XP {g}
{1&a} Options Name = This computer
{1&b} Options Name = That Computer
{2&f} Options Name = Workstation
and so on..? |
1079
|
Tue Apr 12 09:30:51 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Other | 2.5.8-3 | Re: XML password files, replication & FreeBSD |
> I have been running ELOG on FreeBSD no problem for a year now,
> but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine
> with a few warnings (see attached logs).
> But has issues with password files, now it shows message "Can't open
> passwords.pwd" for all my logbooks. It did convert the password files to
> xml format. I had a good hard look at file permissions and config file with
> no luck. So I went back a version and compiled 2.5.7-1 which works just
> fine with old password files. So something with XML & FreeBSD?...
Hard to say. The simplest would be if I could debug this.
> Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
> When I run a ./elogd -C http://elog.blah.here:88 it clones the config file
> just fine, also seems to copy over all logbook entries.
> But once I look through them there's a fault with one of the fields it
> copies over, so entries never show up.
>
> It should be:
> ========================================
> Date: Tue Mar 01 19:41:29 2005
> In reply to: 24
> Work done by: someuser
> Work done at (dd/mm/yy hh:mm): 1/03/05 3:30pm
> Downtime duration: 0 min
> Planned: Yes
> Reason: Normal work
> Attachment:
> Encoding: plain
>
> But once cloned it looks like this:
> ========================================
> Date: Tue Mar 01 19:41:29 2005
> In reply to: 24
> Work done by: someuser
> Work done at (dd/mm/yy hh: m): 1/03/05 3:30pm
> Downtime duration: 0 min
> Planned: Yes
> Reason: Normal work
> Attachment:
> Encoding: plain
>
>
> For some reason it looses the "m" so line 4 instead of having
> "hh:mm" has "hh: m"
Your problem is that the attribute "Work done at (dd/mm/yy hh:mm)" which
contains a ":". This character is not allowed in attributes. Unfortunately I did
not document this (and even didn't know this until now... (;-) ). So you should
use the new option
Type Work done at = datetime
this gives you at the entry mask fields for day/month/year/hour/minute to fill
out, so you don't have to write it directly into the attribute. Another option
would be to use
Comment Work done at = Please enter as (dd/mm/yy hh:mm)
which just displays a comment below the attribute in the entry mask.
- Stefan |
1078
|
Tue Apr 12 09:13:27 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.5.8-2 | Re: Default Date Format |
> I downloaded the latest file and installed but the version number stayed at
> 2.5.8-2 and did not change to -3.
Sorry I forgot to increase the version number in the source code. So don't worry.
> Also is there a way to change the display of the default date. It uses
> allot of space in the date column.
Date format = %A, %B %d
see manual! |
1077
|
Tue Apr 12 01:05:20 2005 |
| G | levineg@med.govt.nz | Bug report | Other | 2.5.8-3 | XML password files, replication & FreeBSD |
Ok this really is 2 questions.
1)
I have been running ELOG on FreeBSD no problem for a year now,
but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine
with a few warnings (see attached logs).
But has issues with password files, now it shows message "Can't open
passwords.pwd" for all my logbooks. It did convert the password files to
xml format. I had a good hard look at file permissions and config file with
no luck. So I went back a version and compiled 2.5.7-1 which works just
fine with old password files. So something with XML & FreeBSD?...
2)
Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
When I run a ./elogd -C http://elog.blah.here:88 it clones the config file
just fine, also seems to copy over all logbook entries.
But once I look through them there's a fault with one of the fields it
copies over, so entries never show up.
It should be:
========================================
Date: Tue Mar 01 19:41:29 2005
In reply to: 24
Work done by: someuser
Work done at (dd/mm/yy hh:mm): 1/03/05 3:30pm
Downtime duration: 0 min
Planned: Yes
Reason: Normal work
Attachment:
Encoding: plain
But once cloned it looks like this:
========================================
Date: Tue Mar 01 19:41:29 2005
In reply to: 24
Work done by: someuser
Work done at (dd/mm/yy hh: m): 1/03/05 3:30pm
Downtime duration: 0 min
Planned: Yes
Reason: Normal work
Attachment:
Encoding: plain
For some reason it looses the "m" so line 4 instead of having
"hh:mm" has "hh: m"
Cheers,
GL. |
Attachment 1: compiling_ELOG_Errors_2.5.7-1.txt
|
===[root] /usr/local/elog #gmake
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elog src/elog.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o regex.o src/regex.c
src/regex.c: In function `regex_compile':
src/regex.c:1193: warning: comparison between signed and unsigned
src/regex.c:1208: warning: comparison between signed and unsigned
src/regex.c:1301: warning: comparison between signed and unsigned
src/regex.c:1326: warning: comparison between signed and unsigned
src/regex.c:1340: warning: comparison between signed and unsigned
src/regex.c:1350: warning: comparison between signed and unsigned
src/regex.c:1362: warning: comparison between signed and unsigned
src/regex.c:1368: warning: comparison between signed and unsigned
src/regex.c:1376: warning: comparison between signed and unsigned
src/regex.c:1612: warning: comparison between signed and unsigned
src/regex.c:1630: warning: suggest explicit braces to avoid ambiguous `else'
src/regex.c:1642: warning: comparison between signed and unsigned
src/regex.c:1650: warning: suggest explicit braces to avoid ambiguous `else'
src/regex.c:1686: warning: comparison between signed and unsigned
src/regex.c:1702: warning: comparison between signed and unsigned
src/regex.c:1730: warning: comparison between signed and unsigned
src/regex.c:1817: warning: comparison between signed and unsigned
src/regex.c:1930: warning: comparison between signed and unsigned
src/regex.c:1936: warning: comparison between signed and unsigned
src/regex.c:1941: warning: comparison between signed and unsigned
src/regex.c:1945: warning: comparison between signed and unsigned
src/regex.c:1949: warning: comparison between signed and unsigned
src/regex.c:1953: warning: comparison between signed and unsigned
src/regex.c:1957: warning: comparison between signed and unsigned
src/regex.c:1961: warning: comparison between signed and unsigned
src/regex.c:1979: warning: comparison between signed and unsigned
src/regex.c:2027: warning: comparison between signed and unsigned
src/regex.c:2031: warning: comparison between signed and unsigned
src/regex.c: In function `compile_range':
src/regex.c:2240: warning: comparison between signed and unsigned
src/regex.c:2242: warning: signed and unsigned type in conditional expression
src/regex.c:2242: warning: signed and unsigned type in conditional expression
src/regex.c: In function `re_match_2':
src/regex.c:3317: warning: comparison between signed and unsigned
src/regex.c:3407: warning: comparison between signed and unsigned
src/regex.c:3431: warning: comparison between signed and unsigned
src/regex.c:3470: warning: empty body in an else-statement
src/regex.c:3484: warning: comparison between signed and unsigned
src/regex.c:3500: warning: comparison between signed and unsigned
src/regex.c:3775: warning: comparison between signed and unsigned
src/regex.c:3775: warning: unused variable `destination'
src/regex.c:3922: warning: comparison between signed and unsigned
src/regex.c:3922: warning: unused variable `destination'
src/regex.c:3975: warning: comparison between signed and unsigned
src/regex.c:3975: warning: unused variable `destination'
src/regex.c:4081: warning: comparison between signed and unsigned
src/regex.c:4114: warning: comparison between signed and unsigned
src/regex.c:4114: warning: unused variable `destination'
src/regex.c:4127: warning: comparison between signed and unsigned
src/regex.c:4127: warning: unused variable `destination'
src/regex.c:4295: warning: comparison between signed and unsigned
src/regex.c: In function `regcomp':
src/regex.c:4770: warning: signed and unsigned type in conditional expression
src/regex.c: In function `regerror':
src/regex.c:4890: warning: comparison between signed and unsigned
src/regex.c: At top level:
src/regex.c:4882: warning: unused parameter 'preg'
In file included from src/regex.c:3838:
src/regex.c: In function `re_match_2':
src/regex.c:4599: warning: passing arg 1 of `bcmp_translate' discards qualifiers from pointer target type
src/regex.c:4599: warning: passing arg 2 of `bcmp_translate' discards qualifiers from pointer target type
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elogd src/elogd.c regex.o
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elconv src/elconv.c
|
Attachment 2: compiling_ELOG_Errors_2.5.8.txt
|
===[root] /usr/local/elog-2.5.8 #gmake
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elog src/elog.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o regex.o src/regex.c
src/regex.c: In function `regex_compile':
src/regex.c:1193: warning: comparison between signed and unsigned
src/regex.c:1208: warning: comparison between signed and unsigned
src/regex.c:1301: warning: comparison between signed and unsigned
src/regex.c:1326: warning: comparison between signed and unsigned
src/regex.c:1340: warning: comparison between signed and unsigned
src/regex.c:1350: warning: comparison between signed and unsigned
src/regex.c:1362: warning: comparison between signed and unsigned
src/regex.c:1368: warning: comparison between signed and unsigned
src/regex.c:1376: warning: comparison between signed and unsigned
src/regex.c:1612: warning: comparison between signed and unsigned
src/regex.c:1630: warning: suggest explicit braces to avoid ambiguous `else'
src/regex.c:1642: warning: comparison between signed and unsigned
src/regex.c:1650: warning: suggest explicit braces to avoid ambiguous `else'
src/regex.c:1686: warning: comparison between signed and unsigned
src/regex.c:1702: warning: comparison between signed and unsigned
src/regex.c:1730: warning: comparison between signed and unsigned
src/regex.c:1817: warning: comparison between signed and unsigned
src/regex.c:1930: warning: comparison between signed and unsigned
src/regex.c:1936: warning: comparison between signed and unsigned
src/regex.c:1941: warning: comparison between signed and unsigned
src/regex.c:1945: warning: comparison between signed and unsigned
src/regex.c:1949: warning: comparison between signed and unsigned
src/regex.c:1953: warning: comparison between signed and unsigned
src/regex.c:1957: warning: comparison between signed and unsigned
src/regex.c:1961: warning: comparison between signed and unsigned
src/regex.c:1979: warning: comparison between signed and unsigned
src/regex.c:2027: warning: comparison between signed and unsigned
src/regex.c:2031: warning: comparison between signed and unsigned
src/regex.c: In function `compile_range':
src/regex.c:2240: warning: comparison between signed and unsigned
src/regex.c:2242: warning: signed and unsigned type in conditional expression
src/regex.c:2242: warning: signed and unsigned type in conditional expression
src/regex.c: In function `re_match_2':
src/regex.c:3317: warning: comparison between signed and unsigned
src/regex.c:3407: warning: comparison between signed and unsigned
src/regex.c:3431: warning: comparison between signed and unsigned
src/regex.c:3470: warning: empty body in an else-statement
src/regex.c:3484: warning: comparison between signed and unsigned
src/regex.c:3500: warning: comparison between signed and unsigned
src/regex.c:3775: warning: comparison between signed and unsigned
src/regex.c:3775: warning: unused variable `destination'
src/regex.c:3922: warning: comparison between signed and unsigned
src/regex.c:3922: warning: unused variable `destination'
src/regex.c:3975: warning: comparison between signed and unsigned
src/regex.c:3975: warning: unused variable `destination'
src/regex.c:4081: warning: comparison between signed and unsigned
src/regex.c:4114: warning: comparison between signed and unsigned
src/regex.c:4114: warning: unused variable `destination'
src/regex.c:4127: warning: comparison between signed and unsigned
src/regex.c:4127: warning: unused variable `destination'
src/regex.c:4295: warning: comparison between signed and unsigned
src/regex.c: In function `regcomp':
src/regex.c:4770: warning: signed and unsigned type in conditional expression
src/regex.c: In function `regerror':
src/regex.c:4890: warning: comparison between signed and unsigned
src/regex.c: At top level:
src/regex.c:4882: warning: unused parameter 'preg'
In file included from src/regex.c:3838:
src/regex.c: In function `re_match_2':
src/regex.c:4599: warning: passing arg 1 of `bcmp_translate' discards qualifiers from pointer target type
src/regex.c:4599: warning: passing arg 2 of `bcmp_translate' discards qualifiers from pointer target type
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -DHAVE_STRLCPY -c -o mxml.o ../mxml/mxml.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -I../mxml -o elogd src/elogd.c regex.o mxml.o
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elconv src/elconv.c
|
1076
|
Mon Apr 11 23:01:37 2005 |
| David Egolf | degolf@fujicolor.com | Question | Windows | 2.5.8-2 | Default Date Format |
Hello,
I downloaded the latest file and installed but the version number stayed at
2.5.8-2 and did not change to -3. I stopped and restarted the service and
reinstalled a couple of times as this is just a demo experimental base I
had it overwrite everything, but it stilled stayed the same.
Also is there a way to change the display of the default date. It uses
allot of space in the date column.
Thanks
David Egolf |
1075
|
Mon Apr 11 21:22:25 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | Linux | 2.5.7-1 | Re: Segmentation fault when searching for empty regex |
I applied a similar fix like you proposed, just omit highlighting at all if I get a
zero length match. Changes committed to CVS. |
1074
|
Mon Apr 11 20:15:01 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.5 8-3 | Re: Lost cfg file |
> Thank you so much for working with me on this. The RSS reader I have been trying
> is at http://www.rssreader.com and is version 1.0.88.0 It is a free RSS reader
> and seems to work very well. It has a username and password system, but I am not
> sure what and how it will support with ELog. I have been successful in reading an
> open logbook with no passwords.
rssreader supports HTTP authentication. So what you have to do is to define a "read
password". Open a dos box, navigate to your elog directory, and enter
elogd -l <logbook> -r <password>
replace <logbook> with your real logbook name and <password> with any password. This
command modifies elogd.cfg and puts your password there in encrypted form.
Next, tell rssreader to use authentication and enter there your password
(authetication name does not matter). See the attachment. Rssreader will then be able
to connect properly to your logbook. |
Attachment 1: rssreader.gif
|
|
1073
|
Mon Apr 11 18:48:18 2005 |
| David Egolf | degolf@fujicolor.com | Question | Windows | 2.5 8-3 | Re: Lost cfg file |
> > I was upgrading to the latest version and I wrote over my cfg file. I
> > still have my database files. Is there a way to put the cfg file back
> > together using the database files as a guide. It did not seem to want to
> > upgrade until I did this and I forgot to copy and then paste the cfg files
> > back. The latest version is now running. Before I did this I was still
> > getting the old version number at the bottom of the main screen. Also I
> > have an RSS reader that can do user name and password, is this possible
> > with Elog if the RSS reader has the ability?
>
> I put an extra dialog box into the installer to prevent overwriting the
> original config file, but unfortunately I cannot prevent people from shooting
> themselves into the foot (;-)
>
> The database files contain at least the attributes. Just open any file with a
> text editor. But the other settings, like "preset <attribute>" etc. are lost.
>
> Concerning teh RSS authentication, I willing to implement this if you tell me
> which reader you are using, so that I can test it. You could also try yourself,
> maybe it works without modification. What you would need is public read access
> via "Guest menu commands" option plus a "Read password". The read password
> prevents again the public read access, but the RSS reader can maybe submit it.
> What the RSS reader certainly cannot do is to fill out the "Login" screen of
> elog, so you need the "Guest menu commands" for sure.
>
> - Stefan
Hello,
Thank you so much for working with me on this. The RSS reader I have been trying
is at http://www.rssreader.com and is version 1.0.88.0 It is a free RSS reader
and seems to work very well. It has a username and password system, but I am not
sure what and how it will support with ELog. I have been successful in reading an
open logbook with no passwords.
Thanks again,
David Egolf |