Thanks for the report. When user is logged out, the whole session becomes invalid. This should be solvable by using nohup or running PHP in screen/tmux.

Thanks.

er, my point is： may be the php process shouldn't quit if echo failed.

the fail of fprintf  does not cause php to quit? why echo is so special and so fragile?

example:
fprintf.php
<?php
fprintf(STDOUT, "hello, world\n");
fclose(STDOUT);
fprintf(STDOUT, "hello, world2\n");
fprintf(STDERR, "hello, world2 in stderr\n");

output:
hello, world
PHP Warning:  fprintf(): 2 is not a valid stream resource in /tmp/t.php on line 4
hello, world2 in stder


however, if change fprintf to echo, php will quit early.

Behavior confirmed: <https://3v4l.org/sJeMB>.

Interestingly, running the script on a debug version of PHP,
won't exhibit this behavior.  Instead, I get:

    hello, world
    bool(true)
    hello, world2
    hello, world2 in stderr

> the fail of fprintf  does not cause php to quit? why echo is so
> special and so fragile?

To begin with, fprintf() explicitly requests the resource, and
notices that it has been closed, so it doesn't actually try to
write anything to stdout (the warning goes to stderr by default).