Account Removal Hooks
Use Eenos removeacct DELETE hooks with captured account data, termination ordering and cleanup limitations.
| Property | Value |
|---|---|
| Function/directory | removeacct |
| Pre scripts | /var/eenos/hooks/removeacct/pre/ |
| Post scripts | /var/eenos/hooks/removeacct/post/ |
| Delivered actions | DELETE |
| Panel label | wap |
The shared account termination routine emits removeacct hooks with panel=wap and action=DELETE for an existing hosting-user record. The hook name is removeacct, not deleteacct.
Payload and timing
data is the account mapping captured before termination, with separate user and primary domain arguments. The pre-hook runs before domain discovery and cleanup. Zone deletion can emit separate dns DELETE hooks for each zone. If DNS deletion fails, termination returns early and the removeacct post-hook is not reached.
The post-hook runs near the end after the cleanup calls and optional service reload, using the earlier captured account mapping. Local user files, home directories and other resources may already be gone. Do not depend on reopening them from a post-hook.
Cleanup and external systems
The routine is not an atomic transaction and reaching post does not prove that every underlying cleanup action succeeded. Use the supplied captured identity and a deliberate reconciliation policy for external resources. Do not irreversibly remove external data from a pre-hook merely because deletion has been requested: later server cleanup can fail. Hook failures cannot veto or roll back account removal.
Script contract
Each script receives command-line key=value arguments: base64-encoded JSON data, uppercase action, lowercase panel and optional domain/user. Use the argument decoder examples and installation guide. Scripts run in lexicographic filename order within each phase. There is no automatic retry, hook-specific timeout or parent-operation veto from a nonzero exit code.