Jump to content

mysqlNewbie

New Members
  • Posts

    3
  • Joined

  • Last visited

    Never

Profile Information

  • Gender
    Not Telling

mysqlNewbie's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. Works like a charm now. Thanks!
  2. Yes, I did do a manual install of the Apache server. I didn't remove those files, just moved them. After I wasn't able to manually start everything, I put them back. I used the installer for phpMyAdmin, and that's what put all the /var/www files in place, including /var/www/phpmyadmin. Now, you said: Secondly, because phpMyAdmin is a web application it requires a http to run, it also requires a MySql server (obviosuly seeing as it is actually an interface to MySql). Are you saying that you need to have the Apache server running for phpMyAdmin-- httpd? Or is http something inside of mySQL that serves up the /var/www/phpmyadmin page, located at http://localhost/phpmyadmin/? Either way, my manual install of Apache wouldn't have an effect on the files in /var/www, because it didn't put them there. So, removing it won't make that go away, and because the manually installed server isn't the one being started at boot time, then that isn't impacted either. I'll still end up with an Apache server running at boot time, serving up some phpmyadmin files for mySQL. So, I guess the outstanding question right now is, does phpmyadmin require an apache server, or not? I could just as easily use the apache server that's being started up in the /var/www directory, I'm just trying to understand what it's doing there, who put it there, and why.
  3. I'm really new to this, but I do know my way a little around Linux. First, the versions of everything.... MySQL: 5.1.40 Apache: 2.2.15 Perl: 5.10.1 phpMyAdmin: 3.2.2.1 Mandriva: 2010 / 2.6.31.5 Kernel I'll admit, on some of this, I just blindly did the installs. Now, mySQL starts at boot-up. I didn't do this, it put the stuff into whatever init.d files it needed. I start X, and open up phpMyAdmin. I can connect, create tables, and everything seems to be working just fine. I type in http://127.0.0.1, and sure enough, it brings up the web page with "It works". Again, I didn't put this in the startup, but there it is, starting up nonetheless. I go to change: /usr/local/apache2/htdocs/index.html ...and refresh the page. No change. After poking around, I find out two things: 1. It's serving up the default page from the following location. This was (I think) done by MySQL and/or phpMyAdmin -- not sure who is doing it. /var/www/html/index.html 2. I have to manually start up my Apache server in: /usr/local/apache2/bin/ ...in order for my non-mySQL Apache server to start. Also, I have to switch the port, because the MySQL one is eating up port 80. So, here are my questions. 1. Can someone confirm if one of the following is happening? a. MySQL depends on Apache running, and it has its own server -- the one started at boot time b. phpMyAdmin depends on Apache running, and it has its own server -- the one started at boot time c. They both need Apache running, and they're getting their own server -- the one started at boot time d. Something else? 2. Because there are now two servers -- the one for my web page, and the other is for the DB stuff -- I won't be able to connect from my web page to the other. Is that true? 3. I would like to be able to not have this thing automatically start every time I boot the computer, but I don't know how to do this. I've pulled the files: /etc/init.d/httpd /etc/init.d/mysqld but then my bootup gets angry at me. And, I don't know how to start these things manually. And I don't know if they're running as services, or as daemons. Or even what's the right way. Help would sure be appreciated. Thanks!!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.