fastcgi and apache httpd.conf
![](https://seccdn.libravatar.org/avatar/27baa448681c4a5c26d14d8f44fbe635.jpg?s=120&d=mm&r=g)
Hi, Has anyone got the mod_fastcgi working under suse8.1? I seem to get it to run , but I think the apps.fcgi are just being treated as plain cgi. The test script which is provided by the fcgi distribution, has a counter in it, and when you reload, the counter is supposed to increment by 1. It dosn't increment for me, but I get no error messages or anything. If you have fcgi working properly, could you please post the appropriate section of httpd.conf? Thanks -- use Perl; #powerful programmable prestidigitation
![](https://seccdn.libravatar.org/avatar/2db2bd336c7dc5448fceef369f2076db.jpg?s=120&d=mm&r=g)
Using SuSE 8.1, MySql database server has been installed. The install_db script runs fine. However, Mysql does not startup when booting. In the runlevel editor, MySQL service hangs if it is started. The kill command has to be used to stop mysql return linux back to a normal condition. To manually start MySql, the command "safe_mysqld --user=root &" works but the standard command "safe_mysqld --user=mysql &" will not start mysql and exists with an error. However installing MySQL from RPMs from mysql.com works with --user=mysql command. Can anyone help me to correct this problem? __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
![](https://seccdn.libravatar.org/avatar/c2cde3b9b469273687bfb6e7c72fc707.jpg?s=120&d=mm&r=g)
On Fri, 20 Dec 2002, Linux World 999 wrote:
Using SuSE 8.1, MySql database server has been installed. The install_db script runs fine. However, Mysql does not startup when booting. In the runlevel editor, MySQL service hangs if it is started. The kill command has to be used to stop mysql return linux back to a normal condition.
I assume you installed the RPMs, then ran the install_db script as root, and finally trid to start MySQL, correct?
To manually start MySql, the command "safe_mysqld --user=root &" works but the standard command "safe_mysqld --user=mysql &" will not start mysql and exists with an error.
This seems to fit with my assumption. It did the same to me in SuSE 7.3 when I ran the install_db script as root. The answer is to not run the install_db script manually. It is run automatically by the startup scripts the first time. Another answer is to modify ownership of the mysql databases. Right now they are only readable and writeable for root (The user that created them), and the mysql user has no access to them. Regards Ole
![](https://seccdn.libravatar.org/avatar/c044c5075a60de3d119592c094323fa3.jpg?s=120&d=mm&r=g)
* Linux World 999
Using SuSE 8.1, MySql database server has been installed. The install_db
Please use your email client properly. If you start a new subject,
start a new thread. You have hijacked this thread:
From: zentara
![](https://seccdn.libravatar.org/avatar/2db2bd336c7dc5448fceef369f2076db.jpg?s=120&d=mm&r=g)
On Friday 20 December 2002 23:43, SuSEnixER wrote:
* Linux World 999
[12-20-02 11:58]: Using SuSE 8.1, MySql database server has been installed. The install_db
Please use your email client properly. If you start a new subject, start a new thread. You have hijacked this thread:
<snip> This was not my intention. Please accept my apologies. Can you advise how a new thread can be started using Kmail? Any help appreciated.
![](https://seccdn.libravatar.org/avatar/c044c5075a60de3d119592c094323fa3.jpg?s=120&d=mm&r=g)
* Linux World 999
On Friday 20 December 2002 23:43, SuSEnixER wrote:
* Linux World 999
[12-20-02 11:58]: Using SuSE 8.1, MySql database server has been installed. The install_db
Please use your email client properly. If you start a new subject, start a new thread. You have hijacked this thread:
<snip>
This was not my intention. Please accept my apologies. Can you advise how a new thread can be started using Kmail? Any help appreciated.
Start a new thread by starting a new message, not replying to an existing message. If you reply to an existing message, you are extending the existing thread. I understand that you gain the list address by responding to an existing message. If that is your intention, delete the "In-Reply-To:" line and change the Subject:. Threading is accomplished by referring the message-id (In-Reply-To: <200212210826.55137.linuxworld999@yahoo.co.uk>. And unless specifically requested otherwise, people reading the list do not want personal replies in addition to list replies. Would you like to receive duplicate posts, especially if you receive 500+ posts/day?? -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org icq#173753138 http://home.indy.rr.com/paka/
![](https://seccdn.libravatar.org/avatar/2db2bd336c7dc5448fceef369f2076db.jpg?s=120&d=mm&r=g)
On Saturday 21 December 2002 15:29, SuSEnixER wrote: <snip>>
I understand that you gain the list address by responding to an existing message. If that is your intention, delete the "In-Reply-To:" line and change the Subject:. Threading is accomplished by referring the message-id (In-Reply-To: <200212210826.55137.linuxworld999@yahoo.co.uk>.
And unless specifically requested otherwise, people reading the list do not want personal replies in addition to list replies. Would you like to receive duplicate posts, especially if you receive 500+ posts/day??
Thank you for your guidance and advice. This is the first time I have subscribed to a mailing list and any help with etiquette is welcome.
![](https://seccdn.libravatar.org/avatar/31cd99395e30a53f253916c2227a4e14.jpg?s=120&d=mm&r=g)
On Friday 20 December 2002 8:55 am, Linux World 999 wrote:
Using SuSE 8.1, MySql database server has been installed. The install_db script runs fine. However, Mysql does not startup when booting. In the runlevel editor, MySQL service hangs if it is started. The kill command has to be used to stop mysql return linux back to a normal condition.
Even if you install SuSE's specific RPM [from their CD/DVD, for instance] it does indeed hang when you try to actually "start" it via the [graphical] runlevel editor -- you should simply set the "start for mode..." settings for 3 or 5 [usually both, actually] and perhaps even mode 2 [though rarely used...] This basically adds link files to the /etc/rcX.d directories of the form S##mysql and K##mysql to start and stop respectively when you change runlevels [i.e., "at the next reboot", for you windows types ;) or if you want to get away from that, learn the [tel]init command...]
To manually start MySql, the command "safe_mysqld --user=root &" works but the standard command "safe_mysqld --user=mysql &" will not start mysql and exists with an error.
Also, if you install w/SuSE's files, there should exist an "rcmysql" link file [I think under /sbin, but basically only in a directory found in "root"'s path -- normal users don't "see" the rc.... commands] these also link to the /etc/rd.d startup files, so the command rcmysql start should "manually" start the service(s). Likewise, the commands rcmysql status rcmysql stop show whether the service is "running" and stop it respectively.
participants (5)
-
Linux World 999
-
Ole Kofoed Hansen
-
SuSEnixER
-
Tom Emerson
-
zentara