sean finney wrote:
so, i'll reassign this bug to user-mode-linux. i notice that this was
kept out of sarge, so thankfully this means that this is not a problem
that should be hitting most people.
No, in fact I don't think it will affect many people. This is not a very
widespread configura
Quick summary:
- good thing is I that it is solved.
- bad thing is that it seems to be kernel-related. read on.
sean finney wrote:
is this an strace from the daemon while it was having the problem you
reported, or after you attempted the various other things you did? it
doesn't look like it'
sean finney wrote:
After upgrading from stable to stable (sarge 3.1 is just stable, I did a dist-upgrade of the machine), everything
works fine, EXCEPT mysql which does not start trowing this error:
Jun 7 23:17:26 muscetta mysqld[13935]: mysqld got signal 11;
that's a segfault. no fu
eady on 2.6.
Unfortunately I CAN'T change that myself, as it is a UML machine set up by an
hosting provider, and due to UML they
provide you the kernel... I warned them too, anyway.
Thanks for the Best Distro on the planet, but please try to help me with this!
:-)
Best Regards,
4 matches
Mail list logo
