| |-4296 sapstart pf=/sapmnt/HA1/profile/HA1_ASCS00_sapro0as | |-4125 /usr/sap/HA1/ASCS00/exe/sapstartsrv pf=/sapmnt/HA1/profile/HA1_ASCS00_sapro0as -D -u ha1adm The result is that the SAP Instance will now stay in the pacemaker system.slice The next one (ONE, 1=one) line in the pam stack, which is in this case pam_systemd.so and by this bypassing the user.slice creation of systemd During a session setup called by su it will check whether the Username provided is in the file /etc/SAPUsers and if yes it will do “success=1”, meaning it will With the su-session file in place, modify the Which contains the names of the SAP Admin Users, in this example, SID is HA1 these would be Session pam_listfile.so item=user sense=allow file=/etc/SAPUsers Session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm Session required pam_unix.so try_first_pass This can be bypassed by modifying the su part of the pam stackĬp /etc/pam.d/common-session /etc/pam.d/su-session As systemd session setup will move any application started with
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |