[IPython-dev] iTorch - Weird issues with mkfifo on linux

[MinRK]

Can you run the server with `--debug`, and post the logs around when the
failure occurs?

On Fri, Jan 16, 2015 at 11:05 AM, Soumith Chintala <soumith at fb.com> wrote:

>  This is not a problem of blocking reads, or the heartbeat stopping, I
> have verified both those parts.
> But I’ll try investigating more into if it’s a system-call/signaling
> weirdness.
> Thanks,
> Soumith
>
>   From: Thomas Kluyver <takowl at gmail.com>
> Reply-To: IPython developers list <ipython-dev at scipy.org>
> Date: Friday, January 16, 2015 at 10:16 AM
> To: IPython developers list <ipython-dev at scipy.org>
> Subject: Re: [IPython-dev] iTorch - Weird issues with mkfifo on linux
>
>    On 15 January 2015 at 19:26, Soumith Chintala <soumith at fb.com> wrote:
>
>> One problem we oncovered is that on certain (or possibly all linux
>> distros) ipython thinks our kernel died, even though it is alive and well.
>
>
>  FIFOs have some bizarre properties which might be related - for
> instance, opening a FIFO for reading will block until something else opens
> it for writing (the open() call itself blocks, not just attempts to read).
> Could it be that an unexpectedly blocking system call is stopping the
> heartbeat and causing IPython to think that your kernel is dead?
>
>  Thomas
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20150116/8fd48d15/attachment.html>