Repository navigation
Laragon 8.6.1 — Technical clarification about Apache graceful shutdown and forced termination #1622
Unanswered
billmelo45-sys
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello Laragon Development Team,
I am using Laragon 8.6.1.60301 on Windows with Apache 2.4.66-260223-Win64-VS18.
I manage Apache manually through the Laragon GUI, using the individual Apache > Start/Stop controls.
Before authorizing a controlled maintenance operation, I need clarification about the shutdown mechanism implemented in this specific Laragon version.
Could you please clarify the following?
How does Laragon identify the exact Apache instance to stop? Does it use the parent process ID, PID file, executable path, or another mechanism?
What mechanism does the individual Apache > Stop command use to request shutdown? For example, Apache's native shutdown mechanism, Windows console control events, a Windows service command, or a dedicated signaling utility?
Does this mechanism request a cooperative/graceful shutdown, allowing Apache to release resources and terminate normally?
How does Laragon wait for and verify that Apache has completely stopped?
Is there a timeout? What happens if Apache does not respond within that period?
Can Laragon use
TerminateProcess,taskkill, or another forced-termination mechanism when stopping Apache? If so, under which conditions, and which processes may be affected?If forced termination is supported, is there a documented way to disable that fallback and report a shutdown failure instead?
Does stopping Apache individually leave MariaDB, other independent Apache instances, and unrelated Windows services running?
Could you confirm whether these behaviors apply specifically to Laragon 8.6.1.60301, or point me to the relevant documentation or implementation?
My objective is to establish a safe, verifiable maintenance procedure without unexpectedly terminating Apache processes or affecting independent services.
A technical explanation or reference to the relevant implementation would be greatly appreciated.
Thank you for your assistance.
Best regards,
Bill Melo
All reactions