The problem is most probably related to the time zone. elogd contains a function:

/* workaround for wong timezone under MAX OSX */
long my_timezone()
{
#if defined(OS_MACOSX) || defined(__FreeBSD__)
   time_t tp;
   time(&tp);
   return -localtime(&tp)->tm_gmtoff;
#else
   return timezone;
#endif
}

If you see only the file name it means that elogd cannot find the file, it's probably in the wrong directory. Have you put it into the "logbooks" directory? Like c:\Program Files\ELOG\logbooks\ ? 

You will not loose your logbook data if you have access rights to the file system where the "elogd" program writes it's data.

The easiest way is to edit there password file directly and then restart "elogd".

But even if you do not dare to edit the files directly, you still can solve the issue from the web interface:

• Create a new account, e.g. user "admin2"
• While logged in as "admin", make this user an administrator: go to "Change config file", add "Admin user = admin, admin2"
• Now log off and then login as "admin2"
• Check that you can do administration, then remove user "admin"
• Create a new user "admin" with proper "Full name" and "Email"
• Now log off and then login as "admin"
• Check that you can do administration, then remove user "admin2"

That should work. Good luck!

Hi All,

I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?

Regards,

Per

I once had problems with the local system account, so I used my own account to start the service and that worked. For trial, you can also start the elogd.exe program manually (not as a service) in a DOS box and see if it can create the password file. 

I forgot to mention, I also have Password file line in elogd.cfg file. Because without password file line, I wouldn't get login screen. I know my test account is not in the main.pwd file. I believe elogd does go to kerberos server to compare password. I just don't get why I get invalid username and password when I entered correct password, while kerberos error (expected) when I enter wrong password.  

Authentication = Kerberos

Kerberos Realm = xxx

Password file = main.pwd

Actually there is no good secure way. What I usually do is to give users admin rights on individual logbooks, then they can change the config of that logbook. Many times adding some attribute is as good as creating new logbooks. Like if you need two logbooks "home" and "work", you can create an attribute "type" and let the type be "home" or "work". With conditional attributes you can make the logbook behave differently for the two values of "type" and get most functionality of two separate logbooks.

- Stefan 

This is possible with conditional attributes. An additional trick would be to not show the text body of an attribute is not selected. This way the user first has to select the attribute, then the text field with the specific preset will show up. The configuration would be something along these lines:

Attributes = Type, Subject
Options Type = One{1}, Two{2}, Three{3}
Show text = 0

{1} Preset text = text1
{2} Preset text = text2
{3} Preset text = text3
{1,2,3} Show text = 1

Of course you have to supply proper text files text1, text2, text3.

- Stefan