nn::ndm::SuspendScheduler FunctionResult SuspendScheduler( bool bAsync = false );
| Name | Description | |
|---|---|---|
| in | bAsync | Specify true to return from the process without waiting for the suspension to complete. Specify this when you do not need to know whether suspension has completed and want to quickly perform the next process. Normally, you should specify false. |
| Value | Description |
|---|---|
| ResultInvalidOperation | There are too many suspend operations. |
Suspends the daemon manager that handles scheduling for all network daemons.
Note: This function halts all CTR background processing. Be fully aware of the side effects and give close attention to the timing of calling this function.
Autonomous network connections and all autonomous daemon operations are suspended while scheduling is suspended. Any daemons currently connected to the network will be disconnected immediately. The requests to stop scheduling are managed by a counter, so they can be nested. This will halt all autonomous network processing. You should thus use Suspend or SuspendDaemons to halt one or more specific daemons unless you have strong reasons not to.
If you want to conduct communication in the foreground using an Internet connection (for example, nn::ac::Connect or nn::friends::Login), only call SuspendScheduler when needed, and when these connections have finished their processing. This will enable you to halt just the features you do not need, without wasted work or resources.
Note: Calling nn::friends::Login immediately after calling SuspendScheduler will cause the system to log out from the friend server and then log back in over a short time frame, which violates the guideline.
CONFIDENTIAL