FAQ: Why is ArcSDE for Linux creating three giomgr processes?
Why is ArcSDE for Linux creating three giomgr processes?
When a thread is created for the first time, Linux makes the current Process Identification (PID) the master thread. The master thread creates and manages two child-threads to execute different parts of the code.
After disconnecting, SDE defunct gsrvr processes occur for each terminated connection because the giomgr does not read that the gsrvr processes were terminated.
The defunct gsrvr processes do not use any memory, and will end when a new connection is spawned or upon running an SDE administration command, such as: sdemon -o status. Knowing there are three processes, with only one using memory, is important when estimating and allocating server resources.