From: JRough on
On Dec 23, 11:21 am, OldSchool <scott.my...(a)macys.com> wrote:
> On Dec 23, 1:09 pm, JRough <jlro...(a)yahoo.com> wrote:
>
>
>
> > On Dec 23, 7:10 am, OldSchool <scott.my...(a)macys.com> wrote:
>
> > > "I need it to be this:
> > > /usr/local/bin:/usr/local/sbin:/usr/local/mysql*/bin:/usr/bin:/bin:/
> > > usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
> > >    .
> > >    .
> > >    .
> > > The mysql* in the path is a sym link to the mysql-5.1.40-osx10.5-
> > > powerpc directory..."
>
> > > As Jon noted, the directory is probably NOT "/usr/local/mysql*", but
> > > rather "/usr/local/mysql".  I'd bet the "*" is an artifact of a GNU
> > > derived "ls" command.  You can find out by trying "cd /usr/local/
> > > mysql".  if that works, remove the "*" from the above...
>
> > > The fact that its a symbolic link doesn't matter one way or the
> > > other...i.e. you can use either (provided the symlink is correctly
> > > entered).
>
> > > one advantage of the using the symlink over the full path is that the
> > > correct full path may change if you subsequently upgrade, while the
> > > symlink *should* remain the same name and always point at the
> > > installation......
>
> > Well thanks that did something.  It does have a sym link so you don't
> > have to type the long directory name.  I was able to try to start the
> > mysql
> > demon but it still seems like it still has some path issues.
>
> > sh-3.2# /usr/local/mysql/bin/mysqld_safe --user=_mysql
>
> > 091223 09:59:48 mysqld_safe Logging to '/usr/local//usr/local/
> > mysql-5.0.82-osx10.5-powerpc/data/janis-roughs-power-mac-
> > g5.local.err'.
> > touch: /usr/local//usr/local/mysql-5.0.82-osx10.5-powerpc/data/janis-
> > roughs-power-mac-g5.local.err: No such file or directory
> > chown: /usr/local//usr/local/mysql-5.0.82-osx10.5-powerpc/data/janis-
> > roughs-power-mac-g5.local.err: No such file or directory
> > 091223 09:59:49 mysqld_safe Starting mysqld daemon with databases
> > from /usr/local//usr/local/mysql-5.0.82-osx10.5-powerpc/data
> > /usr/local/mysql/bin/mysqld_safe: line 100: /usr/local//usr/local/
> > mysql-5.0.82-osx10.5-powerpc/data/janis-roughs-power-mac-g5.local.err:
> > No such file or directory
> > /usr/local/mysql/bin/mysqld_safe: line 137: /usr/local//usr/local/
> > mysql-5.0.82-osx10.5-powerpc/data/janis-roughs-power-mac-g5.local.err:
> > No such file or directory
> > 091223 09:59:49 mysqld_safe mysqld from pid file /usr/local//usr/local/
> > mysql-5.0.82-osx10.5-powerpc/data/janis-roughs-power-mac-g5.local.pid
> > ended
> > /usr/local/mysql/bin/mysqld_safe: line 100: /usr/local//usr/local/
> > mysql-5.0.82-osx10.5-powerpc/data/janis-roughs-power-mac-g5.local.err:
> > No such file or directory
>
> > Is it still the $PATH variable that is wrong and it can't find
> > something or what?  What is line 100 & 137 about? ....
>
> lines 100 and 137 appear to refer to those lines in the script " /usr/
> local/mysql/bin/mysqld_safe"
>
> the remainder of the errors seem to indicate that it can't find:
> "/usr/local//usr/local/mysql-5.0.82-osx10.5-powerpc/data/'
>
> to create files in...but the path names are so attrocious, I'm not
> sure..I'd bet it is supposed to be:
>
> "/usr/local/mysql-5.0.82-osx10.5-powerpc/data/"
>
> which may mean there was an error / typo in the installation process,
> or that the environment variables aren't properly set-up in the
> profile

Would that be the $PATH environment variable? That is probably it.
How can I fix it? I guess what I added is wrong. I changed it above
because of the sym link.
When I did pwd in the mysql symlink directory I got this path so I
changed my $PATH from this:
export PATH="/usr/local/bin:/usr/local/sbin:/usr/local/mysql*/bin:
to
this:
/usr/local/bin:/usr/local/sbin:/usr/local/mysql*/bin:/usr/bin:/bin:/
usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
Now I know the * should be deleted for reasons mentioned above so
should I just take off the appendage and will that fix it?THANKS,
I don't know why adding the sym link changed it from the first to the
second but I can just change it back I guess.
From: OldSchool on
its probably NOT that PATH variable thats hosed at this point. You
need to find the script you ran, and examine the two lines noted (100
and 137??). You may see a reference to a variable in that line. If
so, thats the one that is currently not right....

As to how it got to be "not right", that could have been done during
installation, or when you set up whatever had to be added
to .profile / .bashrc or whatever.

I'm not familiar w/ the install process for MySQL, nor do I have it
installed anywhere handy, so I can't look into what else might be
wrong. You might also try to locate a MySQL forum / group. They
might have somebody that's seen similar issues before, and knows what
it is off the top of there head.

you could also run "env > somefile" and see if you can indentify a
variable that's set to something begining "/usr/local//usr/
local......."