Ok, i compiled the code below and ran it,
it prints out:

timezone: 134513644

but in BASH shell if i type DATE, then this is the output:
Mon Oct 18 09:44:00 NZDT 2004
so it does know about NZ time...

Anyone got ideas?

Thanks all.
G.


> > Date:  Mon, 11 Oct 2004 12:26:28 -3736512
> 
> The timezone offset (-3736512) is obtained from the "timezone" variable, which
> is initialized with the tzset() function inside elogd. See "man tzset" for
> details. It looks like if the timezone on your FreeBSD box is not correctly
> defined. 
> 
> Try to compile and execute following C program:
> 
> #include <stdio.h>
> #include <time.h>
> 
> main()
> {
>    tzset();
>    printf("timezone: %d\n", timezone);
> }
> 
> This should print something like "timezone: -3600". If not, you might consider
> defining the "TZ" environment variable. Maybe some FreeBSD expert knows some
> details about this.

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.

> > 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.

Anything I could send you to help 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

Ok, i see, the problem for me now is that this attribute name has been in use for 
half a year or so by me. So now I have 100's of logbook entries with the old name 
in them, if I change it's name then all old logbook entries will show up with that 
field blank. I'm not sure if there's an easy way to change that attribute's name in 
100's of entries in 10's of logbooks, because I wouldn't want to try doing that by 
hand.. Any ideas? (i'm no good at scripting something like that 4 sure)

Thanks,
G.

Hi I am running elog on windows 2022 server and trying to use ldap for Auth.

No matter what i do I cannot get it to authenticate against the DC.

Invalid user name or password!

11-May-2022 17:09:15 [xxx.xxx.xxx.xxx] {TrainingHouse1} LOGIN user "xxxxx" (attempt)

Using an LDAP browser I can connect to the DC without issue so not firewall.

Not sure what I am doing wrong.

[global]
port = 5050
Page title = Elog Training
Entries per page = 25
Password file = password.pwd
List page title = Elog Training
Login page title = Elog Training
Show top groups = 0
Logbook tabs = 0
Menu commands = Back, New, Find, Download, Logout
List Menu commands = New, Find, Logout
Self register = 0
Max content length = 100000
Allow password change = 0
Enable attachments = 0
Show attachments = 0
Hide attachments = 1
List after submit = 1
Logout to main = 0
Allowed encoding = 5
Default encoding = 1
Welcome title = Elog Training LogBook.
## Welcome title = <font size=5 color=white>Elog Training LogBook </font><img src="elog.png">
Summary lines = 5
Summary line length = 100
Search all logbooks = 0
Refresh = 300
Login expiration = 0
Reply string = 
Suppress default = 2
Thread display = $category entered by $author on $Entry time
Thread icon = Icon
Preset on reply author = $long_name
All display limit = 300
Start page = ?last=31
Bottom text =
Bottom text login = <font size=5 color=Red><center></br>ELOG Training web site</center></font>

[ADTrainingHouse1]
Hidden = 0
Authentication = LDAP, File
LDAP server = ldap://xxxxxx.xxxxx.xxxx.xxxx.xxxx.au:389
LDAP userbase = OU=Users,OU=CP,DC=xxxx,DC=xxxx,DC=xxxx,DC=xxxx,DC=au
LDAP login attribute = uid
LDAP register = 0
Theme = default
Comment =Training House 1 LogBook
Preset Author = $long_name
Locked Attributes = Author
Attributes = Category, Codes, Residents Involved, Medical, Synopsis, Event Date, Author
Options Synopsis = Yes, No
MOptions Medical = Yes
MOptions Residents Involved = Pleaseadd, Test User
Extendable options = Residents Involved
Style Synopsis Yes = background-color:yellow
Style Medical Yes = background-color:green
Type Event Date = datetime
Preset Event Date = $datetime
Date format %A %B %d %Y %H:%M 
List Display = ID, Event Date, Category, Medical, Codes, Residents Involved, Synopsis, Date, Author
MOptions Category = Assault, Death, Fire, Illness, Inappropriate Sexualised Behaviour, Injury To Child, Injury To Staff, Property Damage, Self-Harm, Substance Misuse, Theft/Loss, Threat
MOptions Codes = MED, ACH, LEGAL, MPR, P/C, PSYCH, MFP, BEH, INC, CM, FAM, INFO, MVT, OBS, POLICE, PROG, ROU, VIS, S/O
Required Attributes = Author, Event Date, Codes
Style Codes MED = background-color:green
Page Title = DCP Elog Training
Reverse sort = 1
Quick filter = Date, Category, Codes, Medical,
Sort Attributes = Event Date
Logfile = traininghouse1.log
Logging level = 3
Bottom text =

Is anyone able to assist with what I am doing wrong is anyone successful used LDAP in windows elog

Is is possible to postdate the Entry Date for an entry?

The documentation lists the ability to forward date an entry, but I don't 
see any ability to backdate an entry (edit the date to a date in the past).

Given that the entry date is part of the logbook entry file structure, it 
wasn't obvious how to make this change.

thanks

fred

Just upgraded (using rpms) elogd from 2.3.5 
I am running on RH 7.3

I noticed that my custom start page did not display the Welcome title icon.
It worked fine in prior elogs.

Here's the syntax of the config file:

Welcome Title = <img src="thumb.gif"><p><font size=4 color=white>Elog</font>
Resource dir = /usr/local/elog/


"thumb.gif" is located in /usr/local/elog, and is readable by all.
I also tried the full file name in src= 
<img src="/usr/local/elog/thumb.gif">  - same result.

any hints?

> > I noticed that my custom start page did not display the Welcome title icon.
> > It worked fine in prior elogs.
> > 
> > any hints?
> 
> Indeed there is a bug, it has to do that some icons wnt into the themes 
> directory and are served now from there. So the bug will fixed in the next 
> version (the fix is already avaliable from CVS). As a temporary workaround 
> you just move your image to the themese/default/ directory and it should 
> work.
> 
> An absolute path like /usr/local/... does not work, because this would open 
> a security hole (someone could access any picture on your computer just by 
> requesting an absolute path in the URL), so I removed that option from the 
> software and the documentation.

I did the work-around (moving icon to theme/default) and it worked. Thanks.

Now if you just port elog over to an apache and mysql enviroment, it would be
perfect!