Hello.
I tried to use slightly modified test examples from latest liblogging but client segfaulted.
It were compiled with gcc 4.1.3 on Ubuntu x86_64 with following changes to source code:
[server side ]
srAPISetOption to
- disable unix domain socket listening
- change udp port listener to 55055 (so it could run without root priveleges)
- enable beep listener
- set beep listener port to 55077
[client side]
- set port in srAPIOpenlog() call to 55077
Here comes the magic:
- after I run ./testsrvr it says
Listening for incoming requests....
port: 55055
but it actually it listen only on 55077 (if I turn off BEEP listener server do not report any errors but do not listen on any ports either)
- after I run ./testdrvr 127.0.0.1 it segfaulted
I obviously doing something wrong so I'll try to explain what I'm trying to achieve:
I need to send set of messages via secure and reliable syslog protocol (BEEP, RFC3195, REPL - anything that is more reliable than plain tcp) to rsyslog running on non-standard port (above 1024).
So far I got troubles with both
- reliability: how to actually send data with libloging to rsyslog listening for RFC 3195 RAW for example
- security: how to send it via TLS tunnel
The final goal is to determine proper set of function calls that will allow me to connect to rsyslog in secure (TLS) and reliable (RFC 3195 RAW) way and send messages from time to time (connection supposed to stay alive as long as possible e. g. in case of network failure it supposed to be transparently restored).
Please advise me if it's actually possible?
Any ideas and links to documentation\examples\code\anything that might bring enlightment will be appreciated.
best regards.


