Custombuild is out of beta.

Is custombuild working fine on your system?

  • Total voters
    110
Can it be changed to not overwrite it the first time if it's already a DA httpd.config?

Jeff
 
No, there isn't such option, because it uses the new config with extra directory and everything is made to use that (suphp configs, aliases etc.). :)
 
Normally would you only run it the first time if you were converting a machine? In other words on a new install using custombuild instead of customapache, would this ever be a problem?

Jeff
 
Does suphp use lots cpu resource? One of my servers was running php4 in CLI, I installed php5 in cgi mode with suphp today, then the server is overloaded, seems the cpu usage is doubled. I switch back to php4 cli then the load is normal again.
possible to build php5 in cgi mode and no suphp? Thanks
 
smtalk said:
Yes, they will be overwritten, but you'll have a backup too.
Click to expand...

so even without doing rewrite_confs old configs are overwritten?

can the default be changed to preserve configs or to only write new .dist files?
 
In httpd 2.0, unlike 1.3, the %b and %B format strings do not represent the number of bytes sent to the client, but simply the size in bytes of the HTTP response (which will differ, for instance, if the connection is aborted, or if SSL is used). The %O format provided by mod_logio will log the actual number of bytes sent over the network.
Click to expand...


looks like need some modification on this issue.
 
Had a look at the logging parts of the config and has both if lines for log_config and log_logio modules, httpd -l shows both modules are loaded so the question is are both been used and conflicting with each other? or just one or the other.

the seperate user httpd configs use the word bytes at the end of the bytes log file and not a flag.
 
Chrysalis said:
so even without doing rewrite_confs old configs are overwritten?

can the default be changed to preserve configs or to only write new .dist files?
Click to expand...

Yes, rewrite_confs is only needed to rewrite configs if you've deleted them etc.
 
ok then if possible I would like an option to set so that I can upgrade apache without needing to worry about my config files been overwritten.
 
Chrysalis, it's impossible to do that in easy way, because everything is done using files in extra directory, it's a goal of custombuild.
 
%b swapped with %O for the default apache 2 configs in custombuild.
The customapache apache 2 httpd.conf is not changed because mod_logio isn't present.

John
 
Please add this little patch for FreeBSD libxml2 and libxslt check

Hello,

I get regularly 'disturbed' by the fact that the build script tries to install libxml2 and libxslt within FreeBSD while they are already installed. The ports from FreeBsD are installed in /usr/local by default and that is where the portinstall also places the files. The check in the current build script is for /usr, so it will never match FreeBSD's default (clean) way of installing third party packages.

Please apply this patch to the build application so that it detects the proper installation of libxml2 and libxslt:

--- build.20070528 Fri May 18 00:36:11 2007
+++ build Tue May 29 00:27:44 2007
@@ -221,7 +221,11 @@
if [ ! -e /usr/include/libxml2 ] || [ ! -e /usr/include/libxslt ]; then

if [ $OS = "FreeBSD" ]; then
- portinstall -i libxml2 libxslt
+ if [ ! -e /usr/local/include/libxml2 ]; then
+ portinstall -i libxml2
+ elif [ ! -e /usr/local/include/libxslt ]; then
+ portinstall -i libxslt
+ fi
else
if [ -e /usr/bin/yum ]; then
yum -y install libxml2-devel libxslt-devel

Note: I splitted both checks because one of the applications might already be installed, and it would be bad to try and install it again ;-)

Thanks!

Kind regards,
Remko
 
smtalk said:
Chrysalis, it's impossible to do that in easy way, because everything is done using files in extra directory, it's a goal of custombuild.
Click to expand...

smtalk of course its possible.

the install script should work like this.

if files dont exist install new ones.
if files do exist preserve current files and either dont install any or install .dist files which the admin can then compare to and see if any changes.

other possibilities is using tags to determine if a older version of the config file is in place.
 
Chrysialis, it's possible (with a rewrite of the whole script), but as I said it's impossible to do in easy way. Because when you install suphp etc. it owerwrites some files in extra dir.
 
why does it need to overwrite a already configured application?

customapache doesnt do this.

I have customised some configs in the extra dir which is why I have a problem with this.
 
Chrysialis, customapache do this, if httpd.conf isn't in /etc/httpd/conf/httpd.conf ;) If you have an extra dir in /etc/httpd/conf then it won't overwrite your configs, because they are compatible with custombuild.
 
Chrysalis, I like your idea of .dist files; similar to updating an RPM.

When you update an RPM, if the new program won't work without the new configuration file the old one gets saved with an extension and the new one gets written; if the new program will work without the new configuration file, but just not with all it's features, the new one gets saved with an extension.

Martynas, I'm not sure why you're so sure it can't easily be done. Do you mean it can't be done without spending an hour or two? Surely that doesn't equate with easily.

As it stands, unless I'm missing something, Custombuild can only be safely used on new servers; it can't be safely used on currently running servers without the admin having to protect the configuration file. Certainly the script could easily protect the file, and with a bit more work even intelligently update the file.

If I'm missing something then please point me to what and where.

Thanks.

Jeff
 
You must log in or register to reply here.
Back
Top