<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic About APache-based Web Server upgrade in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093279#M540907</link>
    <description>On HP-UX 11.11, it is default to install Apache-based web server 2.0.49.&lt;BR /&gt;&lt;BR /&gt;If upgrading from 2.0.49 to the newest version 2.0.59, do I need to swremove the old version first? Is there any document from HP?</description>
    <pubDate>Tue, 19 Feb 2008 05:55:12 GMT</pubDate>
    <dc:creator>Tim_ct</dc:creator>
    <dc:date>2008-02-19T05:55:12Z</dc:date>
    <item>
      <title>About APache-based Web Server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093279#M540907</link>
      <description>On HP-UX 11.11, it is default to install Apache-based web server 2.0.49.&lt;BR /&gt;&lt;BR /&gt;If upgrading from 2.0.49 to the newest version 2.0.59, do I need to swremove the old version first? Is there any document from HP?</description>
      <pubDate>Tue, 19 Feb 2008 05:55:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093279#M540907</guid>
      <dc:creator>Tim_ct</dc:creator>
      <dc:date>2008-02-19T05:55:12Z</dc:date>
    </item>
    <item>
      <title>Re: About APache-based Web Server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093280#M540908</link>
      <description>The Jun 07 media already contains&lt;BR /&gt;hpuxwsApache  A.2.0.58.00    HP-UX Apache-based Web Server &lt;BR /&gt;&lt;BR /&gt;and I guess the later media releases have newer versions.&lt;BR /&gt;&lt;BR /&gt;swinstall will manage the update - so simply install the newer version.</description>
      <pubDate>Tue, 19 Feb 2008 06:55:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093280#M540908</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-02-19T06:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: About APache-based Web Server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093281#M540909</link>
      <description>so how about the configuration files, will they  be override? Anyone have experience doing the upgrade?</description>
      <pubDate>Tue, 19 Feb 2008 10:00:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093281#M540909</guid>
      <dc:creator>Tim_ct</dc:creator>
      <dc:date>2008-02-19T10:00:43Z</dc:date>
    </item>
    <item>
      <title>Re: About APache-based Web Server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093282#M540910</link>
      <description>I did the upgrade(not the same versions you mention), and my config files were fine, but i made a full backup of my apache config dir.&lt;BR /&gt;&lt;BR /&gt;Make a a backup just in case!!</description>
      <pubDate>Tue, 19 Feb 2008 13:14:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093282#M540910</guid>
      <dc:creator>likid0</dc:creator>
      <dc:date>2008-02-19T13:14:48Z</dc:date>
    </item>
    <item>
      <title>Re: About APache-based Web Server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093283#M540911</link>
      <description>Although the upgrade does preserve some files, it *WILL* overwrite those which are less used.&lt;BR /&gt;&lt;BR /&gt;For example, the last update I did a few weeks ago to fix a security issue scrapped php.ini and apachectl which were customized, so better make a backup and try it on your test environment first.&lt;BR /&gt;&lt;BR /&gt;Olivier</description>
      <pubDate>Wed, 20 Feb 2008 00:13:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093283#M540911</guid>
      <dc:creator>Olivier Masse</dc:creator>
      <dc:date>2008-02-20T00:13:24Z</dc:date>
    </item>
    <item>
      <title>Re: About APache-based Web Server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093284#M540912</link>
      <description>It is always helpful if you can test the&lt;BR /&gt;upgrade before applying it to a production server. E.g. Apache 2.0.58.01&lt;BR /&gt;needed Perl 5.8.8 to be installed first, with Apache shut down. However the new 'apachectl' startup file wanted to use Perl 5.6.1&lt;BR /&gt;&lt;BR /&gt; There are often issues like that to deal&lt;BR /&gt;with after an Apache upgrade.</description>
      <pubDate>Wed, 20 Feb 2008 12:04:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093284#M540912</guid>
      <dc:creator>David Nixon</dc:creator>
      <dc:date>2008-02-20T12:04:14Z</dc:date>
    </item>
    <item>
      <title>Re: About APache-based Web Server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093285#M540913</link>
      <description>thanks for the information.&lt;BR /&gt;Sorry I am not experience with apache.&lt;BR /&gt;&lt;BR /&gt;I hit another problem when trying to stop apache.&lt;BR /&gt;&lt;BR /&gt;As I know start and stop of apache is control by apachectl start/stop. &lt;BR /&gt;But when I execute "apachectl stop", "httpd" is still in "ps -f".&lt;BR /&gt;&lt;BR /&gt;It is not related to the upgrade issue, but I just curious to know, beside apachectl status, is there any way to check apache is currently running?</description>
      <pubDate>Wed, 20 Feb 2008 15:25:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093285#M540913</guid>
      <dc:creator>Tim_ct</dc:creator>
      <dc:date>2008-02-20T15:25:45Z</dc:date>
    </item>
    <item>
      <title>Re: About APache-based Web Server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093286#M540914</link>
      <description>httpd is also used for other functionality.&lt;BR /&gt;&lt;BR /&gt;apachectl will control the server listen on port 80, but apache based server is also used for example&lt;BR /&gt;ISEE - port 5060&lt;BR /&gt;SMH  - port 2301/2381&lt;BR /&gt;&lt;BR /&gt;Read the "ps -ef" output carefully, SMH related server looks like this (for this example):&lt;BR /&gt;&lt;BR /&gt;hpsmh 19628 19616  0 16:49:06 ?         0:00 /opt/hpws/apache/bin/httpd -k start -DSSL -f /opt/hpsmh/conf/sm</description>
      <pubDate>Wed, 20 Feb 2008 15:57:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093286#M540914</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-02-20T15:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: About APache-based Web Server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093287#M540915</link>
      <description>Thanks for your replay. Information is very useful!</description>
      <pubDate>Sat, 23 Feb 2008 13:33:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-apache-based-web-server-upgrade/m-p/5093287#M540915</guid>
      <dc:creator>Tim_ct</dc:creator>
      <dc:date>2008-02-23T13:33:23Z</dc:date>
    </item>
  </channel>
</rss>

