TSA does it on another way. In this case processes are started directly by *sapctrl*. This way sapstart process is not available in process list.
Okay, but why this is important for me?
sapstart writes sapstart.log in /usr/sap/<SID>/(A)SCS/work folder. This is then evaluated by sapcontrol Webmethod calls, among others by GetProcessList or GetSystemInstanceList ones. Whatever process ID (PID) is found in sapstart.log it will be used for determining the status of process. Even if the process is running, just because it has been started by TSA earlier, but the PID does not match the one is sapstart.log sapcontrol will give GRAY status - in some cases it could be RED as well. SAP Management Console uses the same methods for displaying process status.This could result in
issues during software update or upgrade (via Software Update Manager a.k.a. SUM)