> Looks like a weird Linux installation. Maybe try to link static:
> 
> gcc -O -static -o elogd elogd.c 
> 
> executable will be much bigger, but maybe work...


Now I have more error. ;(

$ gcc -O -static -o elogd elogd.c
elogd.c:792: warning: conflicting types for built-in function `logf'
/tmp/ccysvxip.o(.text+0x12f3): In function `setgroup':
: warning: Using 'initgroups' in statically linked applications requires at runtime
the shared libraries from the glibc version used for linking
/tmp/ccysvxip.o(.text+0x12cd): In function `setgroup':
: warning: Using 'getgrnam' in statically linked applications requires at runtime
the shared libraries from the glibc version used for linking
/tmp/ccysvxip.o(.text+0x1351): In function `setuser':
: warning: Using 'getpwnam' in statically linked applications requires at runtime
the shared libraries from the glibc version used for linking
/tmp/ccysvxip.o(.text+0x2fe97): In function `server_loop':
: warning: Using 'gethostbyaddr' in statically linked applications requires at
runtime the shared libraries from the glibc version used for linking
/tmp/ccysvxip.o(.text+0x15ca): In function `sendmail':
: warning: Using 'gethostbyname' in statically linked applications requires at
runtime the shared libraries from the glibc version used for linking

Maybe you can post your elogd build.... just for me. :)

nait.

> Now I have more error. ;(
> 
> Maybe you can post your elogd build.... just for me. :)

I compiled one (just for you :))), available at

http://midas.psi.ch/elog/download/tar/elogd-snapshot.gz

Unzip it and rename it to "elogd". But if you have problems with missing shared C
libraries, I cannot guarantee that it works. In that case you have to wait for the next
official release.

> I compiled one (just for you :))), available at
> 
> http://midas.psi.ch/elog/download/tar/elogd-snapshot.gz
> 
> Unzip it and rename it to "elogd". But if you have problems with missing shared C
> libraries, I cannot guarantee that it works. In that case you have to wait for the next
> official release.

Thank you very much.... it work.  
nait.

> 
> Thank you very much.... it work.  
> nait.

Hi Stefan,

It has a bug. The filter will fail on the initial page of the logbook. 

example,

on http://10.10.10.10:10/mylogbook/  
when select category filter the system will return
      http://10.10.10.10:10/myylogbook/&category=hardware which is bad

on http://10.10.10.10:10/mylogbook/page or page1/page2 etc..other then the initial page,
when select category filter the system return the correct result.
      http://10.10.10.10:10/mylogbook/page?category=hardware.

I have not tested 2.5.3.

nait.   

> It has a bug. The filter will fail on the initial page of the logbook. 
> 
> example,
> 
> on http://10.10.10.10:10/mylogbook/  
> when select category filter the system will return
>       http://10.10.10.10:10/myylogbook/&category=hardware which is bad
> 
> on http://10.10.10.10:10/mylogbook/page or page1/page2 etc..other then the initial page,
> when select category filter the system return the correct result.
>       http://10.10.10.10:10/mylogbook/page?category=hardware.
> 
> I have not tested 2.5.3.

You should, it has been fixed in 2.5.3 :-)))

> 
> You should, it has been fixed in 2.5.3 :-)))

Usual problem for me. There is no elogd binary file in the tar.gz file. 
I remember you used to include it. :) 

nait.

After going through the code of the Python API (https://github.com/paulscherrerinstitute/py_elog/blob/master/elog/logbook.py) I tried the following:
$ python3
>>> from passlib.hash import sha256_crypt
>>> sha256_crypt.hash( 'foobaa', salt='', rounds=5000)[4:]
'waa2sT6eBt.qk0wsucX/nxU5GcqffqlEx6ja5Lg1OR5'
>>> from datetime import datetime
>>> datetime.now().timestamp()
1599039390.964989
$ curl -F cmd=Submit -F exp=labor -F unm=florian -F upwd='waa2sT6eBt.qk0wsucX/nxU5GcqffqlEx6ja5Lg1OR5' -F Encoding=plain -F When=1599039390.964989 -F Author=curl -F Subject="curl test" -F Category=General -F Type=Diary -F Text="foo baa" http://localhost:8080/test/

This worked. It seems to me, that the "-u" option from Curl is not working for elog.

Cheers,
Florian

This is correct. The elogd daemon needs username and password in parameters "unm" and "upwd". The password must be SHA256 encoded, so best is to grab it from the password file. This way one does not have to send clear text passwords over the network.