- ggCircuit Help Center
- ggLeap User Manual
- Start Up Commands
-
ggLeap User Manual
- Point of Sale
- User Management
- Configuring games and apps
- Troubleshooting
- PC Management
- Console Management
- Client Orders
- Financial Reports and Statistics
- ggCrypto
- ggLeap Basics
- Client Customization
- ggLeap Settings
- Start Up Commands
- Prize Redemption
- ggLeap Client
- Web Admin Settings
- Single Sign On (SSO)
- Game License Management
- PC and User Groups
- Getting Started with ggLeap
- Activity Tracker
- Employee Management
- Guest Functions
- ggMobile
-
ggRock User Manual
- Troubleshooting - ggRock
- Troubleshooting - Network
- Administration - Debian OS
- Administration - Windows
- Troubleshooting - Hardware
- Installation - Debian OS
- Troubleshooting - Boot
- Administration - ggRock
- General
- Administration - Games
- Installation - ggRock Server Application
- Administration - Network
- Troubleshooting - Windows
- Troubleshooting - ggLeap
- Administration - ggLeap
- Troubleshooting - Games
-
ggLeap Product Tours
-
ggLeap AtHome
How to keep child process of an app that launched from startup command alive.
ggLeap kills all apps that it did not intentionally start so we need to make ggLeap start the app to avoid this
In this example we will use a miner app because most miners launch cmd.exe.
-
Add the miner in the startup command
-
Since it is launching cmd.exe we also need to add cmd.exe in the startup commands
-
it should be long running, and should have the same trigger type as the miner.
-
Example setup