Hello, I am running 8.1 to run several virtual domains (apache 1.3). I have run quite a few apache servers before, but I am used to manually managing the httpd.conf file. I am giving SuSE config a try -- seems like a decent tool to manage certain variables for apache. I have a quick question about the httpd.conf files: SuSE's documentation states that, if using SuSEconfig, one should not manually edit httpd.conf, as this will cause a failure when running md5check sums. Fair enough. So then, is it safe/acceptable to manually edit the httpd.conf.SuSEconfig? For example, I want to run my apache server in inted mode -- normally, I would set this in httpd.conf; now I set this in httpd.conf.SuSEconfig? Thanks, Dominic
* Dominic Maraglia;
Hello,
I am running 8.1 to run several virtual domains (apache 1.3). I have run quite a few apache servers before, but I am used to manually managing the httpd.conf file. I am giving SuSE config a try -- seems like a decent tool to manage certain variables for apache. I have a quick question about the httpd.conf files:
SuSE's documentation states that, if using SuSEconfig, one should not manually edit httpd.conf, as this will cause a failure when running md5check sums. Fair enough. So then, is it safe/acceptable to manually edit the httpd.conf.SuSEconfig?
No it would not make a difference since it will not be parsed. On the other hand you can have couple of options a) create your config files which include just the changes you want and then mention these config files in the /etc/sysconfig/apache HTTPD_CONF_INCLUDE_FILES="/etc/httpd/mirrors.conf" and then run SuSEconfig --module apache b)Your second option is editing the /etc/init.d/apache file and changing the configuration it parses ( point it to your own) Of the above two I would go with the first one
For example, I want to run my apache server in inted mode -- normally, I would set this in httpd.conf; now I set this in httpd.conf.SuSEconfig?
I would not do it this way but if you really want to have it run by inetd then 1) insserv -r /etc/init.d/apache This will remove the start and stop symlinks in various runlevels 2) edit your inetd.con or xinetd.conf and you are all set -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
* Dominic Maraglia;
on 06 Nov, 2002 wrote: I am running 8.1 to run several virtual domains (apache 1.3). I have run quite a few apache servers before, but I am used to manually managing the httpd.conf file. I am giving SuSE config a
Hello Togan, try -- seems like a decent tool to manage certain
variables for apache. I have a quick question about the httpd.conf files:
SuSE's documentation states that, if using SuSEconfig, one should not manually edit httpd.conf, as this will cause a failure when running md5check sums. Fair enough. So then, is it safe/acceptable to manually edit the httpd.conf.SuSEconfig?
No it would not make a difference since it will not be parsed. On the other hand you can have couple of options
a) create your config files which include just the changes you want and then mention these config files in the /etc/sysconfig/apache
HTTPD_CONF_INCLUDE_FILES="/etc/httpd/mirrors.conf"
and then run SuSEconfig --module apache
I performed exactly this actions -- I have not touched, at all, any of the default apache conf files. I vi'ed /etc/sysconfig/apache, and added HTTPD_CONF_INCLUDE_FILES="/etc/httpd/virt_hosts"; I also changed the HTTPD_PERFORMANCE=slim to thick. I then ran SuSEconfig --module apache which produced this output: ATTENTION: You have modified /etc/httpd/httpd.conf. Leaving it untouched... You can find my version in /etc/httpd/httpd.conf.SuSEconfig... Including /etc/httpd/virt_hosts.164 ATTENTION: You have modified /etc/httpd/suse_loadmodule.conf. Leaving it untouched... You can find my version in /etc/httpd/suse_loadmodule.conf.SuSEconfig... ATTENTION: You have modified /etc/httpd/suse_addmodule.conf. Leaving it untouched... You can find my version in /etc/httpd/suse_addmodule.conf.SuSEconfig... Installing new /etc/httpd/suse_include.conf Installing new /etc/httpd/suse_define.conf Installing new /etc/httpd/suse_text.conf Finished. So, I find this very confusing as, in fact, I have not touched any of the above mentioned files. Maybe I am missing something, but this seems odd. Any thoughts? Dominic --- [This E-mail scanned for viruses by Declude Virus]
On 11/07/2002 04:47 AM, Dominic Maraglia wrote:
So, I find this very confusing as, in fact, I have not touched any of the above mentioned files. Maybe I am missing something, but this seems odd.
Any thoughts?
Maybe you have updated apache, and the conf files were created with rpmnew extension. Check /etc/httpd. I had similar errors after an update. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace God, I am what I am.
Hello Joe, On 11/07/2002 04:47 AM, Dominic Maraglia wrote:
So, I find this very confusing as, in fact, I have not touched any of the above mentioned files. Maybe I am missing something, but this seems odd.
Any thoughts?
Maybe you have updated apache, and the conf files were created with rpmnew extension. Check /etc/httpd. I had similar errors after an update.
Good idea, however I have not updated the apache install. I installed apache, made a few minor changes to /etc/sysconfig/apache, ran SuSEconfig --module apache and no joy. This is rather toubling as this is on a produciton server... Thanks for the input. Dominic --- [This E-mail scanned for viruses by Declude Virus]
On Wed, Nov 06, 2002 at 04:44:00PM -0800, Dominic Maraglia wrote:
Hello Joe,
On 11/07/2002 04:47 AM, Dominic Maraglia wrote:
So, I find this very confusing as, in fact, I have not touched any of the above mentioned files. Maybe I am missing something, but this seems odd.
Any thoughts?
Maybe you have updated apache, and the conf files were created with rpmnew extension. Check /etc/httpd. I had similar errors after an update.
Good idea, however I have not updated the apache install. I installed apache, made a few minor changes to /etc/sysconfig/apache, ran SuSEconfig --module apache and no joy. This is rather toubling as this is on a produciton server...
I would also think that an update with config files that were _never modified_ would be the most likely reason. (SuSEconfig is a bit stupid in this case, it wouldn't need to store an MD5 sum when the file has never been modified, would it? I can't think of any other explanation right now. (Are there any rpmnew/rpmsave files in /etc/httpd/?) Please check the differences between the files and the *.SuSEconfig editions. That should shed light on it. Peter
On Wed, Nov 06, 2002 at 11:35:00AM -0800, Dominic Maraglia wrote:
SuSE's documentation states that, if using SuSEconfig, one should not manually edit httpd.conf, as this will cause a failure when running md5check sums. Fair enough. So then, is it safe/acceptable to manually edit the httpd.conf.SuSEconfig?
In a way, it is always safe because due to the stored md5sum SuSEconfig will notice that the file is modified by someone else, and refrain from changing that particular file. Also, it is by all means acceptable -- you just need to be aware that SuSEconfig's service will no longer be available afterwards (for that particular file). But as you usually will start out with a fresh configuration, adapted by SuSEconfig to your needs, and from then on do not really need it any longer, this might not be worrying you at all. As Togan pointed out it is a good idea to put the local configuration into other files instead of scattering it into httpd.conf. This is also the method I prefer, for 2 reasons: First, you keep the overview about your own configuration. (Note that apache first reads the complete config, before it starts to assemble it, so the order is often not important.) Second, there will be a time when your httpd.conf will be replaced by a fresh one, either by a major version upgrade, or maybe with the migration to another system. Then you will be glad if you kept your own stuff separately! Nevertheless in many cases you'll still find yourself doing one or two changes to httpd.conf itself (some things can't be overridden once they are set, like CustomLog). But these small changes will be easy to merge into another new httpd.conf. Especially if you use version control, which can be as easy as "ci -l httpd.conf" and "rcsdiff -u ...". Then again, as SuSEconfig does change only a few places in httpd.conf itself, you may want to change things yourself and still use SuSEconfig... just remove the file /var/adm/SuSEconfig/md5/etc/httpd/httpd.conf and SuSEconfig will ignore your changes. In doubt compare SuSEconfig's version with the current file, e.g.: diff -u /etc/httpd/httpd.conf /etc/httpd/httpd.conf.SuSEconfig Peter
participants (4)
-
Dominic Maraglia
-
Joe & Sesil Morris (NTM)
-
poeml@cmdline.net
-
Togan Muftuoglu