Any known issues running in Win Server 2008 R2, 64 bit environment? We sometimes lose connection with the Elog app (ssl) and wonder if due to 64bit or other factor in this set up. A forum search does not explicitly reveal any clues however I did find an entry from someone posting a similar question without a response yet (#67061).

Hi Stefan,

I'm having a problem with 'Preset Text' now behaving differently in the latest release (2.9.1)?
My config file for example has always had: 'Preset Text = This is a test.', previously 'This is a test' was put
verbatim into the text area, now it seems to think whatever follows 'Preset Text =' is always a file and I end
up with 'File <i> This is a test. <i> cannot be found'?

I did notice a 'Print warning if "preset text" file cannot be found' line in the latest release notes, does this
now mean wherever I have used the method above I will now need to make a text file to match?

I'm using them embedded in conditional attributes if that makes any difference?

Thanks for your help.

localhost$ svn diff elog.spec

> Hi Stefan,
> 
> I'm having a problem with 'Preset Text' now behaving differently in the latest release (2.9.1)?
> My config file for example has always had: 'Preset Text = This is a test.', previously 'This is a test' was put
> verbatim into the text area, now it seems to think whatever follows 'Preset Text =' is always a file and I end
> up with 'File <i> This is a test. <i> cannot be found'?
> 
> I did notice a 'Print warning if "preset text" file cannot be found' line in the latest release notes, does this
> now mean wherever I have used the method above I will now need to make a text file to match?
> 
> I'm using them embedded in conditional attributes if that makes any difference?
> 
> Thanks for your help.

Thanks for reporting this bug. I fixed it in SVN revision 2447.

I'm trying to debug an issue with elogd (2.9.1) and was reminded that using the "-v" option exposes
user passwords. This wasn't a huge problem for us in the past, but we're now using kerberos authentication,
meaning that the exposed username/password applies to lots of sensitive systems within our university.


I'd suggest that the "-v" option hide passwords. If they need to be revealed for debugging
purposes, make that a separate (and very well documented) option. Maybe something like:
"--really-include-passwords-as-clear-text-in-log-output". :)

> I'd suggest that the "-v" option hide passwords. If they need to be revealed for debugging

As a work around, I've changed the elogd startup script to do:

        /usr/local/sbin/elogd -v -c /usr/local/elog/elogd.cfg 2>&1 | perl -ne '$|=1; if ( $_ =~ /name="upassword"/
) {<>; <>;} else { print "$_";}' > /var/log/elog 2>&1 &

That simply throws away lines that match the pattern:

    name="upassword"

and the following 2 lines (the last of which contains the password).

I was wondering if anyone out there has had any success with importing XML data into ELOG. Using the XML schema which I derive from the EXPORT data from ELOG into XML format or creating the file from scratch, I either blowup the system and have to restart elogd or it doesn't work and says, XML file doesn't contain ELOG_LIST element (which I create and it still doesn't work).

Basically, I am trying to take spreadsheet data, convert it into XML and upload it as a logbook so I don't have to perform lots of data entry. I also tried .CSV but have had no luck. 

Any thoughts or ideas? 

What happens if you just export as .CSV and then import that file again. Does that work?

If not, can you post your .CSV file here and I will have a look.

Stefan