From: John v. G. <jo...@gr...> - 2005-03-19 09:59:29
|
Hello again list, I've been running dl (1.2.2) in the default config for a while now, only did some port jobs on the firewall and this works fine. (Thanks to Heiko again!) Now I'd like to extend the firewall with Apache and MySQL to (try to) run Postnuke. I found apache in the services menu, and tried to configure it, made an /home dir, pointed the dirs right but it wouldn't go right. Sometimes I got a got connection, other times it just wouldn't work. Don't know why. I dont want to serve the internet yet, just local will do. Could anyone point some newbie docs for me or give me some pointers in the right direction? TIA John |
From: Bruce S. <bw...@ar...> - 2005-03-19 18:21:27
|
> I've been running dl (1.2.2) in the default config for a while now, > only did some port jobs on the firewall and this works fine. (Thanks > to Heiko again!) > > Now I'd like to extend the firewall with Apache and MySQL to (try to) > run Postnuke. I found apache in the services menu, and tried to > configure it, made an /home dir, pointed the dirs right but it > wouldn't go right. Sometimes I got a got connection, other times it > just wouldn't work. Don't know why. > > I dont want to serve the internet yet, just local will do. Could > anyone point some newbie docs for me or give me some pointers in the > right direction? You'll have to edit the Apache configuration file(s) to make it run. /etc/apache2/httpd.conf (I think) The config is huge and takes awhile, but if you have problems check the apache log files to find out what's wrong. (the log file locations are defined in the config file) And if you don't understand anything in the config file, see http://www.apache.org/ - BS |
From: John v. G. <jo...@gr...> - 2005-03-19 19:43:31
|
Bruce Smith wrote: >> I've been running dl (1.2.2) in the default config for a while now, >> only did some port jobs on the firewall and this works fine. (Thanks >> to Heiko again!) >> >> Now I'd like to extend the firewall with Apache and MySQL to (try to) >> run Postnuke. I found apache in the services menu, and tried to >> configure it, made an /home dir, pointed the dirs right but it >> wouldn't go right. Sometimes I got a got connection, other times it >> just wouldn't work. Don't know why. >> >> I dont want to serve the internet yet, just local will do. Could >> anyone point some newbie docs for me or give me some pointers in the >> right direction? > > > You'll have to edit the Apache configuration file(s) to make it run. > /etc/apache2/httpd.conf (I think) Yes, that's it. And I did :-) > > The config is huge and takes awhile, but if you have problems > check the apache log files to find out what's wrong. > (the log file locations are defined in the config file) Yes they are, and I had read them... Just didn't make much sense to me. > > And if you don't understand anything in the config file, see > http://www.apache.org/ Ok Bruce, I suppose you're telling me to be more persistent and basicly just to go figure it out. Perhaps you're right. I will give it another go, I'm going to start this service up again, and make it work this time! (And if not, I'll be back! And I'll bring the logs!) Thanks for the push (well needed)! Sincerly, john |
From: Bruce S. <bw...@ar...> - 2005-03-19 20:17:39
|
> > And if you don't understand anything in the config file, see > > http://www.apache.org/ > > Ok Bruce, I suppose you're telling me to be more persistent and basicly > just to go figure it out. Not exactly. All you said was: it wouldn't work and you don't know why. Well, I don't know why either, and you haven't come close to supplying enough information for someone to figure out your problem. So, I gave you a place to start looking for the cause of your problem (the log files). > Perhaps you're right. I will give it another go, I'm going to start > this service up again, and make it work this time! You definitely have to be persistent if you want to get it working. (unless you want pay a consultant $100/hour to do it for you :) > (And if not, I'll be back! And I'll bring the logs!) The more information you can supply, the better chance we have of helping you figure out your problem. - BS |
From: John v. G. <jo...@gr...> - 2005-03-20 07:12:58
|
Bruce Smith wrote: >>(And if not, I'll be back! And I'll bring the logs!) > > > The more information you can supply, the better chance we have of > helping you figure out your problem. This machine's harddisk died on me while trying. I'll have to replace it and might as well upgrade to 1.2.4 now. Only good thing is that it spoofed my main machine so that one's now directly connected. Perhaps this disk was the source of my problems? Thanks again for your replies Bruce, and I'll let you know when it works! Regards, john |
From: Bruce S. <bw...@ar...> - 2005-03-20 13:24:20
|
> >>(And if not, I'll be back! And I'll bring the logs!) > > > > The more information you can supply, the better chance we have of > > helping you figure out your problem. > > This machine's harddisk died on me while trying. I'll have to replace it > and might as well upgrade to 1.2.4 now. Upgrading is generally extremely easy if you let the auto-upgrade scripts do the work for you. Of if you're talking about starting over from scratch, then this is the perfect time to go to 1.2.4. :-) > Only good thing is that it spoofed my main machine so that one's now > directly connected. > > Perhaps this disk was the source of my problems? Perhaps. We may never know. BTW, the "S.M.A.R.T." package is included on DL to monitor hard drive health. Might be worth running if your HDD contains important data. - BS |
From: John v. G. <jo...@gr...> - 2005-03-20 19:12:45
|
Bruce Smith wrote: > Of if you're talking about starting over from scratch, then this is the > perfect time to go to 1.2.4. :-) I was :-) Basicly I'm just running a default config, a couple of NIC settings, a MAC addres and a port to forward and that's it. >> >>Perhaps this disk was the source of my problems? > > > Perhaps. We may never know. > > BTW, the "S.M.A.R.T." package is included on DL to monitor hard drive > health. Might be worth running if your HDD contains important data. It just contained the etc.tar.bz2. The other disk is a scsi that is not recognized by the system and needs a module to run. That also means my etc is on a floppy now :-( I find that's rather slow... Anyway, I don't have important data, but thanks for the tip, might be nice to include anyway, just for fun :-) On 1.2.4 I'm getting a couple of boot errors regarding the GRSecurity parameters: rand_ip_ids, rand_isns, rand_rpc these yield: No such file or directory. It seems to work allright though. The scsi drive is to hold the swap and home dir but still having trouble to with the LVM. I made a mistake creating it and am searching for the right way of getting rid of it again. Vgreduce won't work while active. Will take some more time I guess. Despite all my (minor) problems I'm yet again baffeled by the ease of setting up devil-linux to a working firewall. And all this flexibility! Gr. john |
From: Bruce S. <bw...@ar...> - 2005-03-21 02:05:29
|
> > BTW, the "S.M.A.R.T." package is included on DL to monitor hard drive > > health. Might be worth running if your HDD contains important data. > > It just contained the etc.tar.bz2. The other disk is a scsi that is not > recognized by the system and needs a module to run. That also means my > etc is on a floppy now :-( I find that's rather slow... Floppies are very slow and unreliable. (and they suck IMO :) A USB memory-stick / flash-drive is much faster to save the config. > On 1.2.4 I'm getting a couple of boot errors regarding the GRSecurity > parameters: rand_ip_ids, rand_isns, rand_rpc these yield: No such file > or directory. > It seems to work allright though. I've had grsecurity on machines running server processes. That's why the i686-server version of DL exists. (it's compiled without grsec) > The scsi drive is to hold the swap and home dir but still having trouble > to with the LVM. I made a mistake creating it and am searching for the > right way of getting rid of it again. Vgreduce won't work while active. > Will take some more time I guess. > > Despite all my (minor) problems I'm yet again baffeled by the ease of > setting up devil-linux to a working firewall. And all this flexibility! I'm glad you like it! :-) - BS |
From: John v. G. <jo...@gr...> - 2005-03-21 19:01:29
|
Bruce Smith wrote: > Floppies are very slow and unreliable. (and they suck IMO :) > A USB memory-stick / flash-drive is much faster to save the config. I'm sure, but this box (586 cyrix) doesn't usb. I keep a copy of the etc on my now working LVM (YES!). Lynn's idea of getting a CF-ide adapter appeals to me as well. > > >>On 1.2.4 I'm getting a couple of boot errors regarding the GRSecurity >>parameters: rand_ip_ids, rand_isns, rand_rpc these yield: No such file >>or directory. >>It seems to work allright though. > > > I've had grsecurity on machines running server processes. That's why > the i686-server version of DL exists. (it's compiled without grsec) I use I486, but haven't looked into these errors yet. >>The scsi drive is to hold the swap and home dir but still having trouble >>to with the LVM. I made a mistake creating it and am searching for the >>right way of getting rid of it again. Vgreduce won't work while active. >>Will take some more time I guess. Creating was allright after all. The problem was (go figure) mounting! Yes first linux lesson forgotten. I think 1.2.2 automounted the lvm for I can't remember I've had this problem before, but 1.2.4 clearly does not. So I put the /home in fstab, and edited rc boot to swapon and voila! Apache now serves as well, although terribly slow on the first request. But PHP doesn't seem to be working. >>Despite all my (minor) problems I'm yet again baffeled by the ease of >>setting up devil-linux to a working firewall. And all this flexibility! > I'm glad you like it! :-) Oh I do, just didn't know you participated in the project. I used to run IPCop which has a nice http config. Dropped out because it was to restrictive and way to slow. DL does more for me and runs faster as well despite being on CD, OK, sometimes the response time isn't as fast as I would like, but once the command has loaded it's fast! IPCop was on HD and still seemed slow. > > - BS cu, john (a hint on php would be welcome!) |
From: Bruce S. <bw...@ar...> - 2005-03-21 19:28:24
|
> Creating was allright after all. The problem was (go figure) mounting! > Yes first linux lesson forgotten. I think 1.2.2 automounted the lvm for > I can't remember I've had this problem before, but 1.2.4 clearly does > not. So I put the /home in fstab, and edited rc boot to swapon and voila! DL should auto-mount all LVM volumes in the VG devil-linux. > Apache now serves as well, although terribly slow on the first request. It's possibly reading the CD for some program/library. (CD's are slower than HDD's) Watch your CD access light when it's slow. > But PHP doesn't seem to be working. AddType application/x-httpd-php .php4 .php3 .phtml .php > > I'm glad you like it! :-) > > Oh I do, just didn't know you participated in the project. Yup. > I used to run IPCop which has a nice http config. Yup, me too. > Dropped out because it was to restrictive and way to slow. Yup, me too. :-) I also used to run FloppyFW, which is nice but WAY to restrictive. (but what do you expect from a floppy based disto :) > DL does more for me and runs faster as well > despite being on CD, OK, sometimes the response time isn't as fast as I > would like, but once the command has loaded it's fast! IPCop was on HD > and still seemed slow. Yeah, and I have other problems with HDD's myself. (energy waster, heat maker, noise maker, high point of failure, hackable, ...) > (a hint on php would be welcome!) Add the above AddType line to your httpd.conf, and name your php files accordingly (with a correct extension). - BS |
From: John v. G. <jo...@gr...> - 2005-03-21 22:47:41
|
Bruce Smith wrote: >>Creating was allright after all. The problem was (go figure) mounting! >>Yes first linux lesson forgotten. I think 1.2.2 automounted the lvm for >>I can't remember I've had this problem before, but 1.2.4 clearly does >>not. So I put the /home in fstab, and edited rc boot to swapon and voila! > > > DL should auto-mount all LVM volumes in the VG devil-linux. That probably it then, on 1.2.2 I followed the docs and named it devil-linux. On 1.2.4 I thought I'd wing it and named it dl :-) No name issue here, just a lazy typist. Do you know where in the rc files this is done? I'd like to add dl in there, and remove my changes. >>Apache now serves as well, although terribly slow on the first request. > It's possibly reading the CD for some program/library. > (CD's are slower than HDD's) Watch your CD access light when it's slow. No, that's not it. There's just a minute! or so delay in displaying the first page, either documentroot/manual or just documentroot is slow. CD light doen not go on for a minute or so, then flashes briefly and there come my page. Any later pages are served lightning fast! >>But PHP doesn't seem to be working. > > > AddType application/x-httpd-php .php4 .php3 .phtml .php That works! (Thanks a 1*10^6!) I don't think I would have found that one without your help! >>I used to run IPCop which has a nice http config. > > > Yup, me too. It still sat on the HD I trashed :-) >>Dropped out because it was to restrictive and way to slow. > > > Yup, me too. :-) > > I also used to run FloppyFW, which is nice but WAY to restrictive. > (but what do you expect from a floppy based disto :) Don't know this one, but have used FreeCisco once :-( Same result > Yeah, and I have other problems with HDD's myself. (energy waster, > heat maker, noise maker, high point of failure, hackable, ...) I'm not too worried about hacks in sense of sensitive data, just plain paranoid as a state of mind. In dealing with the internet I find this a rather healthy view! As for noise, since my server is in my bedroom I kill it before going to bed! D*mn those fans really bug me! >>(a hint on php would be welcome!) > > > Add the above AddType line to your httpd.conf, and name your php files > accordingly (with a correct extension). I did, as stated above, and thanks again for your help, (and chat as well!) > > - BS Regards, john. |
From: Bruce S. <bw...@ar...> - 2005-03-22 00:32:17
|
> > DL should auto-mount all LVM volumes in the VG devil-linux. > > That probably it then, on 1.2.2 I followed the docs and named it > devil-linux. On 1.2.4 I thought I'd wing it and named it dl :-) > No name issue here, just a lazy typist. > > Do you know where in the rc files this is done? I'd like to add dl in > there, and remove my changes. Yes, I know where it's done (I wrote some of that code). But it's a REALLY BAD idea to modify it. Then the next time I modify the code, you will either lose your changes, or you will miss my updates. Just use "vgrename" to change the name of your VG to devil-linux. > >>But PHP doesn't seem to be working. > > > > AddType application/x-httpd-php .php4 .php3 .phtml .php > > That works! (Thanks a 1*10^6!) I don't think I would have found that one > without your help! It pays to have a working Apache from another distro, and the command "diff". :-) > >>I used to run IPCop which has a nice http config. > > > > Yup, me too. > > It still sat on the HD I trashed :-) Good place for it. ;-) - BS |
From: John v. G. <jo...@gr...> - 2005-03-24 19:31:37
|
Bruce Smith wrote: Hi Bruce, back at it again! >>>DL should auto-mount all LVM volumes in the VG devil-linux. >> >>That probably it then, on 1.2.2 I followed the docs and named it >>devil-linux. On 1.2.4 I thought I'd wing it and named it dl :-) > Yes, I know where it's done (I wrote some of that code). But it's a > REALLY BAD idea to modify it. Then the next time I modify the code, > you will either lose your changes, or you will miss my updates. > > Just use "vgrename" to change the name of your VG to devil-linux. Ok, did that, removed my changes, and IT WORKS! OK, firewall's up, apache up, php up... MySQL won't start. It's in the boot up but doen't say OK. Typing './mysqld start' in init.d/ does nothing more. I found the config my.cnf tried creating a socket in a writable dir but no go... I'm stuck again! TIA -john |
From: Bruce S. <bw...@ar...> - 2005-03-24 20:02:24
|
> > Just use "vgrename" to change the name of your VG to devil-linux. > > Ok, did that, removed my changes, and IT WORKS! Cool! > OK, firewall's up, apache up, php up... Cool, cool, cool! :-) > MySQL won't start. It's in the boot up but doen't say OK. > > Typing './mysqld start' in init.d/ does nothing more. I found the config > my.cnf tried creating a socket in a writable dir but no go... I'm stuck > again! Sorry, but I've never tried running mysql on DL. Hopefully someone else can help. - BS |
From: John v. G. <jo...@gr...> - 2005-03-24 23:31:33
|
Bruce Smith wrote: >>MySQL won't start. It's in the boot up but doen't say OK. >> >>Typing './mysqld start' in init.d/ does nothing more. I found the config >>my.cnf tried creating a socket in a writable dir but no go... I'm stuck >>again! > > > Sorry, but I've never tried running mysql on DL. > Hopefully someone else can help. Does anybody? I use a totaly standard 1.2.4 DL, just selectes MySQL at the service menu, but the server won't start.... Gr. John |
From: Martin H. <ma...@ho...> - 2005-03-25 05:22:43
|
Zitat von Bruce Smith <bw...@ar...>: > > MySQL won't start. It's in the boot up but doen't say OK. > > > > Typing './mysqld start' in init.d/ does nothing more. I found the config > > my.cnf tried creating a socket in a writable dir but no go... I'm stuck > > again! > > Sorry, but I've never tried running mysql on DL. > Hopefully someone else can help. ---snip root@r-lan:~ # cat /etc/Devil-release Devil-Linux 1.2.4-i486 root@r-lan:~ # /etc/init.d/mysqld start Starting MYSQL Server: root@r-lan:~ # /etc/init.d/mysqld stop Shutting down MYSQL Server: [ ATTN ] Service doesn't seem to be running root@r-lan:~ # ---snap HTH, #m -- -------------------------------------- http://www.hotze.com/ - we connect you |
From: Les H. <se...@at...> - 2005-03-25 16:18:55
|
Martin Hotze wrote: > Zitat von Bruce Smith <bw...@ar...>: > > >>>MySQL won't start. It's in the boot up but doen't say OK. >>> >>>Typing './mysqld start' in init.d/ does nothing more. I found the config >>>my.cnf tried creating a socket in a writable dir but no go... I'm stuck >>>again! >> >>Sorry, but I've never tried running mysql on DL. >>Hopefully someone else can help. > > > ---snip > root@r-lan:~ # cat /etc/Devil-release > Devil-Linux 1.2.4-i486 > root@r-lan:~ # /etc/init.d/mysqld start > Starting MYSQL Server: > root@r-lan:~ # /etc/init.d/mysqld stop > Shutting down MYSQL Server: [ ATTN ] > Service doesn't seem to be running > root@r-lan:~ # > ---snap > > HTH, > > #m > > > > To learn what is going on on your system you need to modify the /etc/init.d/mysqld script. Look in the "start" stanza of the case statement and you will see a line that looks like: $DAEMON $PARAMETER &> /dev/null & What that does is dump all the error messages in the bit bucket. Make a backup copy of the script and then remove the "&> /dev/null" from that line. Then run it with the "start" option. You should see several error messages relating to the failure to create an error log in /usr/var. These messages come from a script called /usr/bin/mysqld_safe which I believe is being run from the CD-ROM. I think you can resolve the problem by placing a copy of mysqld_safe in writable storage and changing where it attempts to create the error log file. Then change the /etc/init.d/mysqld script to point to the new version of mysqld_safe. Hope this helps - it should at least get you started. ---- Les Hazelton |
From: Les H. <se...@at...> - 2005-03-25 16:34:18
|
Les Hazelton wrote: > Martin Hotze wrote: > >> Zitat von Bruce Smith <bw...@ar...>: >> >> >>>> MySQL won't start. It's in the boot up but doen't say OK. >>>> >>>> Typing './mysqld start' in init.d/ does nothing more. I found the >>>> config >>>> my.cnf tried creating a socket in a writable dir but no go... I'm stuck >>>> again! >>> >>> >>> Sorry, but I've never tried running mysql on DL. >>> Hopefully someone else can help. >> >> >> >> ---snip >> root@r-lan:~ # cat /etc/Devil-release >> Devil-Linux 1.2.4-i486 >> root@r-lan:~ # /etc/init.d/mysqld start >> Starting MYSQL Server: >> root@r-lan:~ # /etc/init.d/mysqld stop >> Shutting down MYSQL Server: [ >> ATTN ] >> Service doesn't seem to be running >> root@r-lan:~ # >> ---snap >> >> HTH, >> >> #m >> >> >> >> > > To learn what is going on on your system you need to modify the > /etc/init.d/mysqld script. Look in the "start" stanza of the case > statement and you will see a line that looks like: > $DAEMON $PARAMETER &> /dev/null & > > What that does is dump all the error messages in the bit bucket. Make a > backup copy of the script and then remove the "&> /dev/null" from that > line. Then run it with the "start" option. You should see several error > messages relating to the failure to create an error log in /usr/var. > > These messages come from a script called /usr/bin/mysqld_safe which I > believe is being run from the CD-ROM. I think you can resolve the > problem by placing a copy of mysqld_safe in writable storage and > changing where it attempts to create the error log file. Then change the > /etc/init.d/mysqld script to point to the new version of mysqld_safe. > > Hope this helps - it should at least get you started. > I know it's bad form to reply to ones' own posts, but I have some additional data. I just tried what I suggested by making a copy of mysqld_safe in the /root directory and pointing its' DATADIR variable to /var/data When I ran "/etc/init.d/mysqld start" mysql started for a period of time and then shut down. This time, the error log had been created and contained messages about permission problems creating some other file. So, you will still need to chase the errors and resolve the config problems. I suspect they resolve around pointers that still point to the read-only CD-ROM section of the filesystem. ----- Les Hazelton |
From: John v. G. <jo...@gr...> - 2005-03-25 17:40:23
|
Les Hazelton wrote: > Les Hazelton wrote: > >> Martin Hotze wrote: >> >>> Zitat von Bruce Smith <bw...@ar...>: >>> >>> >>>>> MySQL won't start. It's in the boot up but doen't say OK. >>> >>> >>> ---snip >>> root@r-lan:~ # cat /etc/Devil-release >>> Devil-Linux 1.2.4-i486 >>> root@r-lan:~ # /etc/init.d/mysqld start >>> Starting MYSQL Server: >>> root@r-lan:~ # /etc/init.d/mysqld stop >>> Shutting down MYSQL Server: >>> [ ATTN ] >>> Service doesn't seem to be running >>> root@r-lan:~ # >>> ---snap That's exactly what happened here. >> To learn what is going on on your system you need to modify the .. > So, you will still need to chase the errors and resolve the config > problems. I suspect they resolve around pointers that still point to the > read-only CD-ROM section of the filesystem. Les, thanks for the pointers. I'll try to work them out. I'll let the list know! John |
From: Les H. <se...@at...> - 2005-03-25 19:46:20
|
Les Hazelton wrote: > Les Hazelton wrote: > >> Martin Hotze wrote: >> >>> Zitat von Bruce Smith <bw...@ar...>: >>> >>> >>>>> MySQL won't start. It's in the boot up but doen't say OK. >>>>> >>>>> Typing './mysqld start' in init.d/ does nothing more. I found the >>>>> config >>>>> my.cnf tried creating a socket in a writable dir but no go... I'm >>>>> stuck >>>>> again! >>>> >>>> >>>> >>>> Sorry, but I've never tried running mysql on DL. >>>> Hopefully someone else can help. >>> >>> >>> >>> >>> ---snip >>> root@r-lan:~ # cat /etc/Devil-release >>> Devil-Linux 1.2.4-i486 >>> root@r-lan:~ # /etc/init.d/mysqld start >>> Starting MYSQL Server: >>> root@r-lan:~ # /etc/init.d/mysqld stop >>> Shutting down MYSQL Server: >>> [ ATTN ] >>> Service doesn't seem to be running >>> root@r-lan:~ # >>> ---snap >>> >>> HTH, >>> >>> #m >>> >>> >>> >>> >> >> To learn what is going on on your system you need to modify the >> /etc/init.d/mysqld script. Look in the "start" stanza of the case >> statement and you will see a line that looks like: >> $DAEMON $PARAMETER &> /dev/null & >> >> What that does is dump all the error messages in the bit bucket. Make >> a backup copy of the script and then remove the "&> /dev/null" from >> that line. Then run it with the "start" option. You should see several >> error messages relating to the failure to create an error log in >> /usr/var. >> >> These messages come from a script called /usr/bin/mysqld_safe which I >> believe is being run from the CD-ROM. I think you can resolve the >> problem by placing a copy of mysqld_safe in writable storage and >> changing where it attempts to create the error log file. Then change >> the /etc/init.d/mysqld script to point to the new version of mysqld_safe. >> >> Hope this helps - it should at least get you started. >> > > I know it's bad form to reply to ones' own posts, but I have some > additional data. I just tried what I suggested by making a copy of > mysqld_safe in the /root directory and pointing its' DATADIR variable to > /var/data > > When I ran "/etc/init.d/mysqld start" mysql started for a period of time > and then shut down. This time, the error log had been created and > contained messages about permission problems creating some other file. > > So, you will still need to chase the errors and resolve the config > problems. I suspect they resolve around pointers that still point to the > read-only CD-ROM section of the filesystem. OK! I have MySQL running on my DL system. It is *extremely* valuable to go to the http://dev.mysql.com web site where you can get the MySQL reference manual in either HTML or PDF format. The chapter on installation is quite useful. I put the original /etc/init.d/mysqld script back with only a small modification near the top. I expanded the variable PARAMETER to include the value "--datadir=/var/data/mysql" which is located on my hard drive. That value gets passed to mysqld_safe so no change is required there. Next, run "ls -l /usr/bin/my*" which will show a group of mysql related commands such as mysql_install_db etc... The reference manual chapter on installation describes the need for mysql user ID and group. These already exist in the /etc/group and /etc/passwd files so that is covered. What you need to do is run "/usr/bin/mysql_install_db --user=mysql" which creates "mysql" and "test" databases. It also outputs several instruction messages to help you get going. And, that's my last words on the subject ---- Les Hazelton |
From: Bruce S. <bw...@ar...> - 2005-03-25 23:02:51
|
> I put the original /etc/init.d/mysqld script back with only a small > modification near the top. I expanded the variable PARAMETER to include > the value "--datadir=/var/data/mysql" which is located on my hard drive. > That value gets passed to mysqld_safe so no change is required there. Is that something we should fix in the main distro? (I'm a postgresql guy and don't know much about mysql) - BS |
From: Les H. <se...@at...> - 2005-03-25 23:50:51
|
Bruce Smith wrote: >>I put the original /etc/init.d/mysqld script back with only a small >>modification near the top. I expanded the variable PARAMETER to include >>the value "--datadir=/var/data/mysql" which is located on my hard drive. >>That value gets passed to mysqld_safe so no change is required there. > > > Is that something we should fix in the main distro? > (I'm a postgresql guy and don't know much about mysql) > I don't think so. In my opinion, for MySQL, or any database to make sense, it needs hard drive support and the --datadir pointer will need to point to where the user places that hard drive directory. Also, there are several other steps that are required to get the MySQL internal database established prior to being ready to support a user database. What might be good is to add a MySQL section to the DL doc. That could include a URL for the web site where I got their reference manual. On second thought, you could change the /etc/init.d/mysqld script to add a comment and a place-holder pointer that the user should change during initial configuration. Maybe a comment in the /etc/sysconfig/config file where the MySQL boot start switch is located would be of value also. Don't know. If you want, I could work on a draft page to add to the DL doc relating to MySQL. I don't see a point in attempting to replace the 1600+ page reference manual, but a quick start page with some commands and pointers might be worth while. Let me know what you think. ---- Les Hazelton |
From: John v. G. <jo...@gr...> - 2005-03-26 14:49:21
|
Hello Les, Les Hazelton wrote: > OK! I have MySQL running on my DL system. It is *extremely* valuable to > go to the http://dev.mysql.com web site where you can get the MySQL > reference manual in either HTML or PDF format. The chapter on > installation is quite useful. The rest of the manual will be as well, I know next to nothing about databases. Last one I used was Dbase III :-) and I never was really good at it! > > I put the original /etc/init.d/mysqld script back with only a small > modification near the top. I expanded the variable PARAMETER to include > the value "--datadir=/var/data/mysql" which is located on my hard drive. > That value gets passed to mysqld_safe so no change is required there. > > Next, run "ls -l /usr/bin/my*" which will show a group of mysql related > commands such as mysql_install_db etc... The reference manual chapter on > installation describes the need for mysql user ID and group. These > already exist in the /etc/group and /etc/passwd files so that is covered. > > What you need to do is run "/usr/bin/mysql_install_db --user=mysql" You forgot to mention one would need to add "--datadir=/var/data/mysql" to that, but it wasn't hard to figure out. > which creates "mysql" and "test" databases. It also outputs several > instruction messages to help you get going. > > And, that's my last words on the subject No further replies needed. This one was just to let you know I got it running thanks to you! Thanks again for your help. regards, john |
From: Les H. <se...@at...> - 2005-03-26 16:05:56
|
John van Grinsven wrote: > Hello Les, > >> You forgot to mention one would need to add "--datadir=/var/data/mysql" > to that, but it wasn't hard to figure out. Oops - sorry about that. >> And, that's my last words on the subject And there was supposed to be a :) at the end of the previous line and I forgot that as well. > No further replies needed. This one was just to let you know I got it > running thanks to you! > > Thanks again for your help. > > regards, john > John, you are quite welcome. I am just glad I was able to help. I have received so much help from others over the years it is good when I get a chance to return the favor. ----- Les Hazelton |
From: Lynn G. <lg...@ad...> - 2005-03-21 06:47:45
|
On Sun, 2005-03-20 at 20:05, Bruce Smith wrote: > Floppies are very slow and unreliable. (and they suck IMO :) > A USB memory-stick / flash-drive is much faster to save the config. Agreed. I just changed to using a USB stick after wearing out a couple of floppy disks. (I'm experimenting, so I reboot a lot.) It works wonderfully, and is much more reliable. Now I'm thinking of removing the floppy drive from the box, so it doesn't make that annoying grinding sound that floppy drives make when they check to see if a floppy is in them at boot time. I just ordered a CF-card-to-IDE adapter, and when it arrives, I'm going to try putting the CD on the CF-card for even more reliability and quietness. Be well... Lynn |