Share this post:
Accepted AnswerWhat a good explanation and thank you.
This just points out another reason why ClearOS community is so great and why I enjoy spending time with ClearOS, the people are always willing to teach new-bees (sounds better than noob) a bit of the basics.
I guess I was confused regarding the file, because before I found the library file, I received a error in the log for " can't execute libsqlmy.so". So the error was just following the flow and couldn't load the library file, than couldn't look for the other library file. I guess it was just following the flow and couldn't run because it didn't have the library.
Accepted AnswerTony EllisOfflineOK - unlike Windows, Nix will not run any executable in the current directory unless a full path is specified either in the path environment or expressly given at the command line
. (one dot) is the current directory
.. (two dots) is the next higher level directory
will run the program called "run_me" that is in the current directory where the command is given
nothing to do with the user or super-user (root)
xxxxxxxxx.so or xxxxxxxxx.so.xxx files are not to be directly run as an executable, but are libraries or a collection of routines are are not called from the command line, but mostly executed by other programs that require routines macros etc within the .so (in most cases). Occasionally they are called, but the calling routine should have set up the necessary environment for them to run...
.so files are somewhat akin to Windows .dll files...
Maybe you know this.
If this command was in a ini file, what would you make of it?
I'm assuming by the "dot / " indicates that it needs to run at root level, is that correct? hmmmm
but when I try to run it ./libsqlmy.so i receive this;
Which at first nearly gave me a heart attack, as I spend most of my weekend fighting exactly that.
But, if I run the default script it works fine (with a few issues) and my own script will not run it. (well not my own script, my "tweeked" script.
Accepted AnswerTony EllisOfflineMaybe opportunity to learn some basic CLI commands?
Anyway - I have a different version - but this should get you going (note the back tick [often on same key as ~ ])
Make sure you have run "updatedb" first (can take a few minutes)
[root@danda ~]# locate libmysqlclient_r
[root@danda ~]# rpm -q --whatprovides `locate libmysqlclient_r`
Note my system is fully up to date...