little glitch with requirements & user docs

By: Stefan Sels user 29 Sep 2016 at 8:47 a.m. CDT

5 Responses
Stefan Sels gravatar
within [vm-preperation-doc](https://www.gluu.org/docs/deployment/#file-descriptor) it sounds as gluu would be installed with a named user (!=root). "Please replace the username with the user that will install Gluu Server." But the next line uses the dash (*) to make it universal. If you than install according to [rhel7-install-guide](https://www.gluu.org/docs/deployment/rhel7/#rhel-7-installation-guide) the chroot won't happen, if you are a non root user, hence the /install will be within /opt/glue... for me it only worked being root.
Rhel72
closed

Answers

By Aliaksandr Samuseu staff 29 Sep 2016 at 9:28 a.m. CDT

Copy
Aliaksandr Samuseu gravatar
Hi, Stefan. > chroot won't happen, if you are a non root user That's expected behaviour, correct. Regarding the fragment you cited and doc you referred to - I'm pretty much sure described procedure implies that you will put name of a user under which some of Gluu's component (like, Apache, or OpenDJ) runs inside of the container there. So you are right, it seems we need to correct it a bit. Thanks for the heads-up. Best regards, Alex.

By Stefan Sels user 30 Sep 2016 at 3:01 a.m. CDT

Copy
Stefan Sels gravatar
and for the pam.d/login part: session required /lib/security/pam_limits.so are you sure the full path is needed? rhel has it within /lib64/security/pam_limits.so and all other .so are referenced by name only.

By Stefan Sels user 30 Sep 2016 at 3:17 a.m. CDT

Copy
Stefan Sels gravatar
you might also remove the /opt/gluu-server-2.4.4/root/.bash_history file from the rhel7 rpm (http://repo.gluu.org/rhel/7/)

By Aliaksandr Samuseu staff 30 Sep 2016 at 5:42 a.m. CDT

Copy
Aliaksandr Samuseu gravatar
Thanks, Stefan. We need to review this part thoroughly, I agree.

By Aliaksandr Samuseu staff 07 Oct 2016 at 5:27 p.m. CDT

Copy
Aliaksandr Samuseu gravatar
Hi, Stefan. I'm closing this ticket. [Issue](https://github.com/GluuFederation/docs/issues/111) is created at github to ensure your input won't pass unnoticed. Thank you for your time and effort, please let us know if any other such issues will catch your eye.

Post an answer