Apache

[marco_186]

i did
swlist|grep -i apache

the result is Null

[Torsten.]

how about the /opt/apache directory ?

By the way, you are now a member of this forum for just about 2 weeks. A lot of your questions are being answered. But people who are helping you are interested in results (or even points). Don't let all of your threads simply die without result. Please have also a look at this thread, if you have the time:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=42657

[marco_186]

Dear Torsten Totzauer
im so sorry cuz i didnt knw about points befor.

thank u soo much for ur help and i will consider that.

thanks

[marco_186]

There is a folder /opt/apache

drwxrwxr-x 3 bin bin 96 Aug 10 10:50 JServ
-r--r--r-- 1 bin bin 13662 Nov 21 2001 LICENSE
-r--r--r-- 1 bin bin 52725 Nov 21 2001 LICENSES_in_bundle
-r--r--r-- 1 bin bin 123 Oct 17 2001 README
drwxr-xr-x 2 bin bin 8192 Aug 10 10:50 bin
drwxr-xr-x 2 bin bin 96 Aug 10 10:50 cgi-bin
drwxr-xr-x 8 bin bin 8192 Aug 10 11:07 conf
drwxr-xr-x 4 bin bin 8192 Aug 10 11:07 htdocs
drwxr-xr-x 3 bin bin 8192 Aug 10 10:50 icons
drwxr-xr-x 3 bin bin 8192 Aug 10 10:50 include
drwxrwxr-x 4 bin bin 8192 Aug 10 10:50 lib
drwxr-xr-x 2 bin bin 8192 Aug 10 10:51 libexec
drwxrwxrwx 2 bin bin 8192 Aug 17 20:24 logs
drwxrwxr-x 5 bin bin 96 Aug 10 10:51 man
drwxrwxr-x 5 bin bin 96 Aug 10 10:51 php
drwxr-xr-x 2 bin bin 96 Aug 10 10:51 proxy
drwxrwxr-x 2 bin bin 8192 Aug 10 10:51 servlets
drwxrwxr-x 9 bin bin 8192 Aug 10 10:51 ssl
drwxrwxr-x 19 bin bin 8192 Aug 10 10:51 webmin

[Torsten.]

That doesn't matter. Just to inform you.

Now you have to decide - keep this old version and configure/use this one or completly remove it and use your new version. It's your decision. You can have only one apache listening on port 80.

[TwoProc · Accepted solution]

Alternatives:
A) Just use the HP one already on your box, and use it as the server you're trying to stand up.
Pros: Already installed, standard patching tools can keep it updated with standard patch maintenance methods for whole box. Also, has a lot of nifty stuff in it that's not included just with Apache.
Cons: If you're not interested in using the extra stuff, it's just junk you'll have to wade through and maintain. HP doesn't seem to patch it's Apache server as fast or as often as apache itself does.
B) Take down the HP server, and run the new one instead.
Pros: You've already installed the new one, and I'm guessing you've got it already setup (at least pro-forma) for the job you want it to do. You can keep it fully patched and current with Apache's recommended changes as often as you wish. It may also be tailored tightly to the job at hand, and have less extraneous "stuff" in it that you're not interested in.
Cons: You may have things running in the HP one that you don't know about that you need. But, regardless - you *really* need to find out.
C) Change new server's port number and run both, or Alternative-C) change old server's port number and run both.
Pros: Both applications live happily ever afterward. The security issues and permissions of one server are totally separate from the other (very good).
Cons: Second application must use a port designator in the URL. You now have TWO Apache servers that you have to keep current for security patches and bug fixes.

That's it - three choices.