On 29/10/14 21:39, Brian Drummond wrote:
Still haven't found a way to identify who owns the
segfaulting pool process, but I haven't given up.
You might find it helpful to install something like corekeeper, then
look for core-dumps in /var/crash/(your numeric uid) which can be
inspected to find
Control: severity -1 important
Hi,
Brian Drummond wrote (25 Oct 2014 12:32:42 GMT) :
The non serious data loss may be a misnomer. It is my assessment
because, if one assumes that a copy finished correctly when it actually
terminated, the client machine is left with an incomplete data set.
On Wed, 2014-10-29 at 20:56 +0100, intrigeri wrote:
Control: severity -1 important
Hi,
Brian Drummond wrote (25 Oct 2014 12:32:42 GMT) :
The non serious data loss may be a misnomer. It is my assessment
because, if one assumes that a copy finished correctly when it actually
terminated,
The non serious data loss may be a misnomer. It is my assessment
because, if one assumes that a copy finished correctly when it actually
terminated, the client machine is left with an incomplete data set.
Non-serious because the files are still there on the server, and it is
possible (tedious!)
4 matches
Mail list logo