Hi Jimmy, no Kerberos is not compiled into the Windows installer. You are the first one asking for that under Windows. All other Kerberos users use Linux so far. You have to compile the Windows version yourelf. This is because there are several versions of Kerberos around and people need differnt libraries. Sorry for that.

/Stefan

The quick fix I found was to uncomment line 10 in the init.d file. (This was tested on a CentOS 6.8 AWS instance.)

. /etc/rc.d/init.d/functions

This will allow the status command to function properly.

Clean install:

[centos@ip-172-31-51-59 ~]$ service elogd status
status: invalid option: -p
 

After uncommenting line 10:

[centos@ip-172-31-51-59 ~]$ service elogd status
elogd (pid  11438) is running...

When you start elog it still won't show that the service started successfully (No 'OK'). If you go to stop the service, it will give you the proper 'OK' indicating it stopped successfully.

So to fix the missing 'OK' (or 'FAILED') we need to update the start section around line 51 as follows:

          touch /var/lock/subsys/elogd
        echo_success
        else
        echo_failure
        fi
        echo
        ;;
 

I've attached my modified init file which I believe corrects the above issues. I will say though that I'm not a programmer so I won't guarantee it's perfect. I haven't checked to see if CentOS 7 works with this modified version. Just checked it on a CentOS 7.2 AWS instance and it also appears to function correctly.

[root@oceana ~]# systemctl status elogd
● elogd.service - SYSV: ELOG is a weblog with integrated database
   Loaded: loaded (/etc/rc.d/init.d/elogd)
   Active: active (running) since Sun 2016-09-18 22:35:44 UTC; 7s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 2263 ExecStop=/etc/rc.d/init.d/elogd stop (code=exited, status=0/SUCCESS)
  Process: 2275 ExecStart=/etc/rc.d/init.d/elogd start (code=exited, status=0/SUCCESS)
 Main PID: 2277 (elogd)
   CGroup: /system.slice/elogd.service
           └─2277 /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg

Sep 18 22:35:44 oceana elogd[2277]: elogd 3.1.1 built Aug  4 20...0
Sep 18 22:35:44 oceana elogd[2277]: revision
Sep 18 22:35:44 oceana elogd[2277]: Falling back to default gro..."
Sep 18 22:35:44 oceana elogd[2277]: Falling back to default use..."
Sep 18 22:35:44 oceana elogd[2277]: CKeditor detected
Sep 18 22:35:44 oceana systemd[1]: Started SYSV: ELOG is a webl....
Sep 18 22:35:44 oceana elogd[2279]: Falling back to default gro..."
Sep 18 22:35:44 oceana elogd[2279]: Falling back to default use..."
Sep 18 22:35:44 oceana elogd[2277]: ImageMagick detected
Sep 18 22:35:44 oceana elogd[2277]: SSLServer listening on port....
Hint: Some lines were ellipsized, use -l to show in full.

The old SysV style commands ('service elogd start|stop|status') also function correctly.

[root@oceana ~]# service elogd stop
Stopping elogd (via systemctl):                            [  OK  ]
[root@oceana ~]# service elogd start
Starting elogd (via systemctl):                            [  OK  ]

Ok, I will include this patch in the distribution.

Stefan

Greetings all.  A few ELOG users have posted issues with ELOG 3.0 and newer not working with a variety of MS Windows operating systems,.
I have also encountered a similar problem in my environment.

For the following operating systems:        
1) Windows XP SP3 (32-bit)           
2) Windows Server 2003 SP 2 (32-bit)
when either elog.exe or elogd.exe are run from command line or file manager, the operating system reports the program is not a Win32 application.

I have other test computers that succesfully ran ELOG 3.0, 3.1 and 3.1.1
1) Windows Vista Enterprise (32-bit)
2) Windows 7 Professional (64-bit) 

Has ELOG 3.x and newer changed in regards to support for MS Windows but is not documented on the
official ELOG documentation?

Any help would be most appreciated.

NOTE: The current production ELOG I use on Windows Server 2003 is 2.92-2475 but I would like to use the
features available on the 3,.x versions.  Unfortunately, I am not able to change my production operating system.
 

I recompiled the executables according to

https://msdn.microsoft.com/en-us/library/jj851139.aspx

and replaces the elog311-1.exe distribution. Can you try if it works? Unfortunately I don't have a XP machine here.

/Stefan

Thank you for recompiling ELOG.  Unfortunately, there is no change in all the test machines
I ran the newly compiled ELOG 3.1.1-1 on.  I will use the 2.x version until our systems move
to a new operating system or I can find someone in my IT department who knows how to compile programs
from the source code. 

If anyone else has suggestions or could compile the source for us to try, please speak up.  There are
many installations of obsolete operating systems in production :
 

Dear Developers

I know this topic i on and off in this forum but it seems the only updated versions of Elog are in the linux binaries. Have anybody been able to compile a windows versions since 2018?

Kind Regards Finn