# tsrm_shutdown() and the CLI SAPI

- Thread: https://externals.io/message/23844
- Original archive: https://news-web.php.net/php.internals/23844
- Started by Frank M. Kromann on 2006-06-01T05:21:06+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #23844 — Frank M. Kromann — 2006-06-01T05:21:06+00:00

URL: https://externals.io/message/23844#23844

> > […]
break 
> > […]
someplace 
> > […]
> 
> Frank's referring to Zeev's three-years-ago decision to simply opt out
of 
> tsrm_shutdown() here... he's suggesting we revert it.
> 
> > […]
nice 
> > […]
> 
> Fine, but breaking working code while you're trying to understand what's

> happening is far from beneficial to our users. Can't we at least #0 it?

There is no need to break code. The shutdown function was commented out
for a reason (crash) when that's fixed we can enable that code again.

- Frank

---

## #23861 — Richard Lynch — 2006-06-01T20:08:18+00:00

URL: https://externals.io/message/23844#23861 · In reply to: #23844

> > […]
>
> > […]
>
> There is no need to break code. The shutdown function was commented
> out
> for a reason (crash) when that's fixed we can enable that code again.

I believe this entire part of this thread stems from a suggestion to
un-comment that on DEVELOPMENT MACHINES.

The OP did only implied the DEVELOPMENT MACHINE, however.

It was only a suggestion that debugging it in CGI would be easier than
in CLI, or at least more common for development users to hit it enough
to FIX it, instead of letting it fester.

It's possible the OP meant to CVS commit such a change, but I would
hope not...

-- 
Like Music?
http://l-i-e.com/artists.htm