| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1063
|
Thu Apr 7 00:51:05 2005 |
 | David Brody | dbrody@echo-inc.com | Question | Windows | 2.5.8.2 | Re: Conditional Attributes/Preset Text |
> > I upgraded from ver 2.5.5-2 to 2.5.8-2 and found that none of my preset text
> > worked any longer. I struggled with it for several hours and then reverted
> > back to 2.5.5-2 and the preset text worked again. I have attached my
> > elgd.cfg file for review. Thanks in advance for your help...
>
> Your config file really helped. You found a bug which happens only if one uses
> conditions with lowercase letters, so that's why nobody else saw it before. I
> fixed it and released V2.5.8-3
Thanks for the information.
ELOG is terrific! |
|
1579
|
Tue Jan 10 00:32:19 2006 |
 | David Brody | dbrody@echo-inc.com | Question | | 2.5.8-2 | Date imports from CSV incorrectly |
When I import from a CSV file, dates formatted as mm/dd/yy always get imported as 12/31/1969
Here are the parameters I am using for dates:
Attributes = Ticket #, Status, Assigned To, Status Date, Install Date, Category, Activity, Environment, Component, TstTrk
Type Status Date = date
Type Install Date = date
Date format = %A, %d %B, %Y
Preset Status Date = $date
Thanks!
DB |
|
1581
|
Tue Jan 10 19:30:09 2006 |
 | David Brody | dbrody@echo-inc.com | Question | | 2.5.8-2 | Re: Date imports from CSV incorrectly |
| David Brody wrote: | When I import from a CSV file, dates formatted as mm/dd/yy always get imported as 12/31/1969
Here are the parameters I am using for dates:
Attributes = Ticket #, Status, Assigned To, Status Date, Install Date, Category, Activity, Environment, Component, TstTrk
Type Status Date = date
Type Install Date = date
Date format = %A, %d %B, %Y
Preset Status Date = $date
Thanks!
DB |
Never mind. I figured it out! |
|
674
|
Thu Aug 19 06:21:38 2004 |
| Dave Becker | dbecker@lanl.gov | Question | Linux | 2.5.4 | write access for elogd |
Newly installed elog gives this response when I try to submit a new record:
New entry cannot be written to directory "./logbooks/Linux/"
Please check that it exists and elogd has write access
I started the daemon. I've not yet assigned passwords -- just checking
things out. How can I create this access to my own directory? |
|
Draft
|
Thu Mar 10 00:16:33 2016 |
| Dave | david.levine@lmco.com | Question | Windows | 2.71 | elogd -m |
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG.
Can anyone tell me why I get this error?
==============================
Here is the command & output:
c:\Program Files (x86)\ELOG>elogd -m
Retrieving entries from "http://166.22.64.201/Equipment Log"...
All entries identical
Retrieving entries from "http://166.22.64.201/System Log"...
Error sending local entry: Error transmitting message |
|
68279
|
Thu Mar 10 00:26:03 2016 |
| Dave | david.levine@lmco.com | Question | Windows | 2.71 | elogd -m Error sending local entry: Error transmitting message |
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG.
Can anyone tell me why I get this error?
==============================
Here is the command & output:
c:\Program Files (x86)\ELOG>elogd -m
Retrieving entries from "http://166.22.64.201/Equipment Log"...
All entries identical
Retrieving entries from "http://166.22.64.201/System Log"...
Error sending local entry: Error transmitting message |
|
446
|
Sun Oct 26 18:32:17 2003 |
| Dave Truesdell | davet@ttfn.com | Comment | Other | elog2.3.9 | Re: FreeBSD Install |
> I got elog 2.3.9 running on FreeBSD 5.1 successfully,
> I compiled elog on a redhat box and then just copied over all the files to
> the FreeBSD box and ELOG just ran with no issues.
> It's been running under heavy use for at least a month now.
FYI- the default "make" on FreeBSD is BSD, not GNU.
The easiest way to build elog on FreeBSD is to install "gmake" (via the port or
package) and type "gmake". That's all it took for me to build a freshly
downloaded copy on 5.1 not 5 minutes ago. |
|
66530
|
Fri Sep 4 20:44:32 2009 |
| Dan | danlei.chao@noaa.gov | Question | Linux | 2.7.7-1 | ELcode in Summary Text |
Hello,
Thank you for such a great piece of software!
When displaying the entries in a log book with Summary view, ELCode is not processed in 'Text'. I know there
is an option called 'Allow HTML", but is there something similar for decoding ELCode in the Summary 'Text' field?
Thank you again,
- Dan |