ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67232
|
Mon Apr 9 19:58:51 2012 |
| Achim Dreyer | ml10352@adreyer.com | Bug report | All | 2.9.1 | wrong version number in spec file |
localhost$ svn diff elog.spec
Index: elog.spec
===================================================================
--- elog.spec (revision 2446)
+++ elog.spec (working copy)
@@ -2,7 +2,7 @@
Name: elog
Summary: elog is a standalone electronic web logbook
-Version: 2.8.1
+Version: 2.9.1
Release: 1
License: GPL
Group: Applications/Networking
|
67233
|
Tue Apr 10 10:08:33 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.9.1 | Re: Preset Text? |
> 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. |
67253
|
Thu Apr 26 23:57:04 2012 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.9.1 | obfuscate password in verbose logging |
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". :) |
67254
|
Fri Apr 27 00:29:56 2012 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.9.1 | Re: obfuscate password in verbose logging |
> 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). |
67349
|
Tue Oct 2 21:58:20 2012 |
| David Chastain | David_Chastain@sra.com | Question | Linux | 2.9.1 | Importing XML |
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? |
67350
|
Wed Oct 3 14:05:15 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.1 | Re: Importing XML |
David Chastain wrote: |
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 |
67356
|
Thu Oct 4 11:35:12 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.1 | Re: Importing XML |
David Chastain wrote: |
[...] 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?
|
I've successfully imported a large amount of entries from old non-ELOG logbooks via XML.
The only problem that I did run into was the date format: ELOG is very restrictive on the imported format; it has to be either "MM/DD/YY(YY) (HH:MM:SS)" or "DD.MM.YY(YY) (HH:MM:SS)".
When you export entries ELOG honours the "Date format" that you've specified in your elogd.cfg, therefore you cannot import the exported file until you reformat the date in the file.
Andreas |
67434
|
Wed Feb 13 15:39:07 2013 |
| Hal Proctor | hproctor2@gmail.com | Question | Windows | 2.9.1 | Locking a Thread |
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books. |