Maybe it's because I'm accessing it through a C Panel SSH Shell that it acts differently than you expected. It doesn't matter anyway… I was able to exit the shell and regain control of my shell. I'm giving up on the upgrade approach for now, so let's consider this conversation concluded.
On Wed, Aug 20, 2014 at 7:28 PM, Reindl Harald <h.rei...@thelounge.net> wrote: > > > Am 21.08.2014 um 01:05 schrieb Augori: > > when I use the bg command, it says > > > > 1 job already in background > > > > and continues to run in the foreground. > > *bullshit* if it is running in foreground you can't enter > anything because your terminal would be blocked, the bg > command only works if you suspend a foreground job > with CTRL+Z to bring it into backgrund > > you really really should learn to post *complete* input > and output what you are doing and honestly consider if > what you are try to do makes any sense > > > On Wed, Aug 20, 2014 at 11:04 AM, Reindl Harald <h.rei...@thelounge.net > <mailto:h.rei...@thelounge.net>> wrote: > > > > Am 20.08.2014 um 16:39 schrieb Augori: > > > However, it's been 12 hours now and the thing is still restarting > in safe > > > mode and I can't tell if it's making progress. The command I > typed was > > > > > > /usr/bin/mysqld_safe --skip-grant-tables& > > > > > > I think I forgot to include the ampersand (&) at the end which > would have > > > made it run in the background. > > > > yes > > > > just type STRG+Z which suspneds the brocess followed by the command > "bg" > > > > > So now I'm seeing output like this the following: > > > ------- > > > ... > > > 0-7f5f68388000 rw-p 00000000 00:00 0 > > > 7f5f68388000-7f5f6838900140820 08:35:01 mysqld_safe Number of > processes > > > running now: 0 > > > 140820 08:35:01 mysqld_safe mysqld restarted > > > -------- > > > > > > It always says Number of processes running now is 0. > > > And it always has the number 140820 on that last line. > > > > > > Should I stop this? If so how? > > > > by just press "STRG+C" > > > > > If I let it go, is it going to take > > > another 2-3 days to restart in regular mode? Does anything have > any > > > alternative suggestions for my original credentials access problem? > > > > mysqld_safe has *nothing* to do with "safe mode" > > > > it's just the profram invoked to start mysqld and > > watch / restart if mysqld dies > > > > if you start an application in forground it will always > > take forever or until it exits which you don't expect > > from a service because - well, you just said to do so > >
