Bug#825394: [libcaf-dev] Fails to link example 'dining_philosophers'

2016-06-01 Thread georg
a self compiled Version of libcaf links perfectly. Also the example taken from https://raw.githubusercontent.com/actor-framework/actor-framework/0.13.2/examples/message_passing/dining_philosophers.cpp is the same as the submitted example. So it seems it is related to the C++ ABI change. Maybe, the

Bug#825394: systemd kill background processes after user logs out

2016-05-28 Thread georg
It is most probably related to this https://github.com/systemd/systemd/issues/2900 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#825394: Maybe related to this post and bugs

2016-05-28 Thread georg
https://bbs.archlinux.org/viewtopic.php?id=204307 https://bugs.freedesktop.org/show_bug.cgi?id=94508 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sys

Bug#805344: systemd: ListenStream=6566 in saned.socket only causes systemd to listen on [::]:6566

2015-11-17 Thread Jens Georg
Did you check if it is actually not reachable over IPv4? IPv6 sockets can also accept IPv4 connections unless configured not to do so. This is controlled system-wide via /proc/sys/net/ipv6/bindv6only which is "0" on my computer (which is the default according to man:systemd.socket(5)). And

Bug#805344: systemd: ListenStream=6566 in saned.socket only causes systemd to listen on [::]:6566

2015-11-17 Thread Jens Georg
I was trying to run sane network scanning through socket activation, but with the provided saned.socket file systemd only listens on a v6 socket. I have to explicitly change ListenStream to 0.0.0.0:6656 to make it listen on v4. Did you check if it is actually not reachable over IPv4? IPv6 so