> On 24 Nov 2015, at 20:03, Matthias Urlichs <matth...@urlichs.de> wrote:
>
> Not reliably. Killing it (systemctl stop), running it manually under
> strace, killing *that* (assuming it doesn't segfault then, which it
> sometimes does) and then restarting it (via systemctl start) always
> works. I've tried gdb, but the stack traces are inconclusive.
Sorry for the dumb question, but are you sure that owserver is *really* dead? I
remember cases in which a daemon was more resilient than a plain “systemctl
stop”. I would always issue a “fuser 4304/tcp” just to be sure there is no
zombie locking up the owserver port… (if 4304/tcp is not available the “new"
owserver will silently refuse to start…)
And what does “owserver hangs” really means? Did you try to catch actual
network traffic with owtap? owdir is not very useful, since it will not print
connection errors… just try ‘owdir -s 127.0.0.1:12345’ or even ‘owdir -s
www.google.com:80’ and you will see no error message.
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
