Find the PID of the process and then do strace -p PID to see what exactly it
is
doing.
Warning you'll probably get a ton of output that means nothing to you.
François
On 16/04/2014, at 23:27, John Cremona john.crem...@gmail.com wrote:
On 16 April 2014 12:18, Francois Bissey
On 16 April 2014 12:49, Francois Bissey
francois.bis...@canterbury.ac.nz wrote:
Hum, yes the parent process is listening for the child but the child seem to
be
mute. Very difficult to do that kind of stuff over email, we'd need to find
what
I know -- and your help in debugging this is
We need the whole log, not just the last two lines.
--
You received this message because you are subscribed to the Google Groups
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To post to this
OK instead of attaching to a running process we'll strace it from the start.
strace -o builddoc.log -f -ff python /home/jec/sage/src/doc/common/builder.py
--no-pdf-links all html
It should produce log files for all the processes created in builddoc.log.$pid
and we'll want these.
Past bedtime in
I've updated the scripts for generating the virtual appliance, its now
based on CentOS 6 which should be less maintenance effort... Updated VM is
here:
http://boxen.math.washington.edu/home/vbraun/vm/sage-6.1.1.ova
http://boxen.math.washington.edu/home/vbraun/vm/sage-6.1.1.ova.sha512
--
You
