Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deliver 64-bit-only Apache 2.4 #4800

Merged
merged 2 commits into from Mar 1, 2019

Conversation

Projects
None yet
3 participants
@pyhalov
Copy link
Contributor

commented Feb 28, 2019

Second part of this PR breaks all our Apache modules, so it depends on module update...

@pyhalov pyhalov force-pushed the pyhalov:apache24 branch 2 times, most recently from f0da076 to b1ab0ee Feb 28, 2019

@pyhalov

This comment has been minimized.

Copy link
Contributor Author

commented Feb 28, 2019

#4801 has to be merged immediately after this.
Also php modules should be rebuilt (TBD)

@pyhalov

This comment has been minimized.

Copy link
Contributor Author

commented Feb 28, 2019

Brief user update instructions:

  1. Update apache 2.4 and modules
  2. Inspect your conf and ini files - mod_event is used by default, 64bit is not set, so ensure to examine all IfDefine 64bit, IfModule prefork.c - these conditions are likely false now. Carefully compare /etc/apache2/2.4/httpd.conf and /etc/apache2/2.4/httpd.conf.new - modules*.load files have gone, modules load is happening in httpd.conf and /etc/apache2/2.4/conf.d/.conf files. Be careful - on update most apache modules will not touch /etc/apache2/2.4/conf.d/.conf files if they have been changed by hands.
  3. Read apache24(1M), it describes apache24 service properties which can be used to manage service.
@jimklimov

This comment has been minimized.

Copy link
Contributor

commented Mar 1, 2019

Do we generate post-upgrade notes files made prominent for people to review after pkg update? Alexander's post above should end up in those too, then.

FWIW, in discussions I advocated for not replacing the existing apache config with a new empty one - having the service broken right after upgrade is the least surprise here, compared to it seemingly loaded with an empty config and then users complaining that the site is wrong.

@pyhalov

This comment has been minimized.

Copy link
Contributor Author

commented Mar 1, 2019

I don't know how to do it in IPS in a sane way. The only thing which comes to mind is to consider such a noitce 'a license' and force user to accept it.

@pyhalov pyhalov force-pushed the pyhalov:apache24 branch from b1ab0ee to d9538f5 Mar 1, 2019

@pyhalov pyhalov requested a review from Mno-hime Mar 1, 2019

@pyhalov pyhalov force-pushed the pyhalov:apache24 branch from d9538f5 to 023b791 Mar 1, 2019

@pyhalov pyhalov merged commit 3d9f324 into OpenIndiana:oi/hipster Mar 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.