Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 633461 Details for
Bug 869695
SAPInstance resource agent should apply configured resource limits for SAP processes
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
[patch]
First draft of a proposed patch that applies resource limits from /usr/sap/sapservices before starting sapstartsrv
bz869695_draft.patch (text/plain), 2.21 KB, created by
Julio Entrena Perez
on 2012-10-25 16:55:26 UTC
(
hide
)
Description:
First draft of a proposed patch that applies resource limits from /usr/sap/sapservices before starting sapstartsrv
Filename:
MIME Type:
Creator:
Julio Entrena Perez
Created:
2012-10-25 16:55:26 UTC
Size:
2.21 KB
patch
obsolete
>--- SAPInstance.orig 2012-10-25 16:44:03.352223149 +0100 >+++ SAPInstance 2012-10-25 17:47:02.917688661 +0100 >@@ -162,6 +162,40 @@ > ! > } > >+# >+# setup_limits: If sapstartsrv needs to be started by this resource agent we need to ensure that any resource >+# limits configured in /usr/sap/sapservices are applied. >+# Since sapstartsrv is started as root and then it downgrades its privileges by calling setuid() and >+# setgid() any PAM limits at /etc/security/limits.conf are not applied. >+# Should sapstartsrv need to be started, we look for values configured at /usr/sap/sapservices (as >+# per SAP note 1437105) and, if found, we apply them before starting sapstartsrv. >+# Instance processes are started by sapstartsrv and will inherit resource limits from it. >+# >+setup_limits() { >+ if [ -r $SAPSERVICES ] >+ then >+ descriptors=`grep "^limit.descriptors" $SAPSERVICES | sed -e "s/limit.descriptors=//" ` >+ if [ -n $descriptors ] >+ then >+ ocf_log info "found valid open file descriptors limit at ${SAPSERVICES}: ${descriptors}, applying..." >+ eval ulimit -n $descriptors >+ fi >+ >+ stacksize=`grep "^limit.stacksize" $SAPSERVICES | sed -e "s/limit.stacksize=//" ` >+ if [ -n $stacksize ] >+ then >+ ocf_log info "found valid stack size limit at ${SAPSERVICES}: ${stacksize}, applying..." >+ eval ulimit -s $stacksize >+ fi >+ >+ datasize=`grep "^limit.datasize" $SAPSERVICES | sed -e "s/limit.datasize=//" ` >+ if [ -n $datasize ] >+ then >+ ocf_log info "found valid process data segment size limit at ${SAPSERVICES}: ${datasize}, applying..." >+ eval ulimit -d $datasize >+ fi >+ fi >+} > > # > # check_sapstartsrv : Before using sapcontrol we make sure that the sapstartsrv is running for the correct instance. >@@ -192,6 +226,8 @@ > if [ $restart -eq 1 ] > then > pkill -9 -f "sapstartsrv.*$runninginst" >+ >+ setup_limits > $SAPSTARTSRV pf=$SAPSTARTPROFILE -D -u $sidadm > > # now make sure the daemon has been started and is able to respond >@@ -571,6 +607,8 @@ > fi > sidadm="`echo $SID | tr '[:upper:]' '[:lower:]'`adm" > >+SAPSERVICES=/usr/sap/sapservices >+ > # What kind of method was invoked? > case "$1" in >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 869695
:
632838
|
632842
| 633461