Thanks for your reply, for some reason this doesn't work for me though. :(
Phil.
2011/1/17 Christian Hofstädtler
> Phil,
>
> On Mon, Jan 17, 2011 at 8:35 AM, Phil Bayfield wrote:
> > For example when I try and stop the server, the init.d script will
> > hang indefinitely and never kill the bac
On 17 January 2011 07:49, Phil Bayfield wrote:
> On 17 January 2011 07:44, wrote:
>
>> Can anyone give me any clues as to why this might happen? Is there a
>>> quit command (I'm already exiting on "QUIT" or empty line from stdin)
>>> that the pipe backend sends? Or maybe this is a bug?
>>>
>>
>
On 17 January 2011 07:44, wrote:
> Can anyone give me any clues as to why this might happen? Is there a
>> quit command (I'm already exiting on "QUIT" or empty line from stdin)
>> that the pipe backend sends? Or maybe this is a bug?
>>
>
> I found this in our perl pipe backend:
>
> LINE: while( <
Can anyone give me any clues as to why this might happen? Is there a
quit command (I'm already exiting on "QUIT" or empty line from stdin)
that the pipe backend sends? Or maybe this is a bug?
I found this in our perl pipe backend:
LINE: while( <> ) {
exit if getppid() == 1; #Exit, cause my p
Hi there,
I've written a custom backend which I'm using with the Pipe backend. It
works perfectly, accepts queries and answers correctly, etc, however for
some reason the processes don't exit cleanly when the server is
stopped/restarted.
For example when I try and stop the server, the init.d scri
