PHP CLI в Windows: обработка команд Ctrl-C?

Question

Как я могу обработать CTRL+C в PHP в командной строке? Pcntl_* функции не работают в Windows.

Answer 1

The following works on unix systems.

Мы можем поймать ключи с помощью stream_get_contents(), но он не улавливает CTRL ключ. Также фильтрация^C не работает.

Что нам нужно сделать, так это поймать сигнал SIGINT posix.

Чтобы подавить CTRL+ c поведение по умолчанию.

Программа не закрывается, вам нужно реализовать другой способ выхода!:

function shutdown(){};
pcntl_signal(SIGINT,"shutdown");

Чтобы обработать CTRL+ c и запустить код перед выходом:

function shutdown(){
    echo "\033c";                                        // Clear terminal
    system("tput cnorm && tput cup 0 0 && stty echo");   // Restore cursor default
    echo PHP_EOL;                                        // New line
    exit;                                                // Clean quit 
}

register_shutdown_function("shutdown");                  // Handle END of script

declare(ticks = 1);                                      // Allow posix signal handling
pcntl_signal(SIGINT,"shutdown");                         // Catch SIGINT, run shutdown()                    

---

Список сигналов POSIX:

Php не сможет поймать SIGKILL.

SIGABRT and SIGIOT
    The SIGABRT and SIGIOT signal is sent to a process to tell it to abort, i.e. to terminate. The signal is usually initiated by the process itself when it calls abort() function of the C Standard Library, but it can be sent to the process from outside like any other signal.
SIGALRM, SIGVTALRM and SIGPROF
    The SIGALRM, SIGVTALRM and SIGPROF signal is sent to a process when the time limit specified in a call to a preceding alarm setting function (such as setitimer) elapses. SIGALRM is sent when real or clock time elapses. SIGVTALRM is sent when CPU time used by the process elapses. SIGPROF is sent when CPU time used by the process and by the system on behalf of the process elapses.
SIGBUS
    The SIGBUS signal is sent to a process when it causes a bus error. The conditions that lead to the signal being sent are, for example, incorrect memory access alignment or non-existent physical address.
SIGCHLD
    The SIGCHLD signal is sent to a process when a child process terminates, is interrupted, or resumes after being interrupted. One common usage of the signal is to instruct the operating system to clean up the resources used by a child process after its termination without an explicit call to the wait system call.
SIGCONT
    The SIGCONT signal instructs the operating system to continue (restart) a process previously paused by the SIGSTOP or SIGTSTP signal. One important use of this signal is in job control in the Unix shell.
SIGFPE
    The SIGFPE signal is sent to a process when it executes an erroneous arithmetic operation, such as division by zero. This may include integer division by zero, and integer overflow in the result of a divide (only INT_MIN/-1, INT64_MIN/-1 and %-1 accessible from C).[2][3].
SIGHUP
    The SIGHUP signal is sent to a process when its controlling terminal is closed. It was originally designed to notify the process of a serial line drop (a hangup). In modern systems, this signal usually means that the controlling pseudo or virtual terminal has been closed.[4] Many daemons will reload their configuration files and reopen their logfiles instead of exiting when receiving this signal.[5] nohup is a command to make a command ignore the signal.
SIGILL
    The SIGILL signal is sent to a process when it attempts to execute an illegal, malformed, unknown, or privileged instruction.
SIGINT
    The SIGINT signal is sent to a process by its controlling terminal when a user wishes to interrupt the process. This is typically initiated by pressing Ctrl+C, but on some systems, the "delete" character or "break" key can be used.[6]
SIGKILL
    The SIGKILL signal is sent to a process to cause it to terminate immediately (kill). In contrast to SIGTERM and SIGINT, this signal cannot be caught or ignored, and the receiving process cannot perform any clean-up upon receiving this signal. The following exceptions apply:

        Zombie processes cannot be killed since they are already dead and waiting for their parent processes to reap them.
        Processes that are in the blocked state will not die until they wake up again.
        The init process is special: It does not get signals that it does not want to handle, and thus it can ignore SIGKILL.[7] An exception from this exception is while init is ptraced on Linux.[8][9]
        An uninterruptibly sleeping process may not terminate (and free its resources) even when sent SIGKILL. This is one of the few cases in which a UNIX system may have to be rebooted to solve a temporary software problem.

    SIGKILL is used as a last resort when terminating processes in most system shutdown procedures if it does not voluntarily exit in response to SIGTERM. To speed the computer shutdown procedure, Mac OS X 10.6, aka Snow Leopard, will send SIGKILL to applications that have marked themselves "clean" resulting in faster shutdown times with, presumably, no ill effects.[10] The command killall -9 has a similar, while dangerous effect, when executed e.g. in Linux; it doesn't let programs save unsaved data. It has other options, and with none, uses the safer SIGTERM signal.
SIGPIPE
    The SIGPIPE signal is sent to a process when it attempts to write to a pipe without a process connected to the other end.
SIGPOLL
    The SIGPOLL signal is sent when an event occurred on an explicitly watched file descriptor.[11] Using it effectively leads to making asynchronous I/O requests since the kernel will poll the descriptor in place of the caller. It provides an alternative to active polling.
SIGRTMIN to SIGRTMAX
    The SIGRTMIN to SIGRTMAX signals are intended to be used for user-defined purposes. They are real-time signals.
SIGQUIT
    The SIGQUIT signal is sent to a process by its controlling terminal when the user requests that the process quit and perform a core dump.
SIGSEGV
    The SIGSEGV signal is sent to a process when it makes an invalid virtual memory reference, or segmentation fault, i.e. when it performs a segmentation violation.[12]
SIGSTOP
    The SIGSTOP signal instructs the operating system to stop a process for later resumption.
SIGSYS
    The SIGSYS signal is sent to a process when it passes a bad argument to a system call. In practice, this kind of signal is rarely encountered since applications rely on libraries (e.g. libc) to make the call for them. SIGSYS can be received by applications violating the Linux Seccomp security rules configured to restrict them.
SIGTERM
    The SIGTERM signal is sent to a process to request its termination. Unlike the SIGKILL signal, it can be caught and interpreted or ignored by the process. This allows the process to perform nice termination releasing resources and saving state if appropriate. SIGINT is nearly identical to SIGTERM.
SIGTSTP
    The SIGTSTP signal is sent to a process by its controlling terminal to request it to stop (terminal stop). It is commonly initiated by the user pressing Ctrl+Z. Unlike SIGSTOP, the process can register a signal handler for, or ignore, the signal.
SIGTTIN and SIGTTOU
    The SIGTTIN and SIGTTOU signals are sent to a process when it attempts to read in or write out respectively from the tty while in the background. Typically, these signals are received only by processes under job control; daemons do not have controlling terminals and, therefore, should never receive these signals.
SIGTRAP
    The SIGTRAP signal is sent to a process when an exception (or trap) occurs: a condition that a debugger has requested to be informed of – for example, when a particular function is executed, or when a particular variable changes value.
SIGURG
    The SIGURG signal is sent to a process when a socket has urgent or out-of-band data available to read.
SIGUSR1 and SIGUSR2
    The SIGUSR1 and SIGUSR2 signals are sent to a process to indicate user-defined conditions.
SIGXCPU
    The SIGXCPU signal is sent to a process when it has used up the CPU for a duration that exceeds a certain predetermined user-settable value.[13] The arrival of a SIGXCPU signal provides the receiving process a chance to quickly save any intermediate results and to exit gracefully, before it is terminated by the operating system using the SIGKILL signal.
SIGXFSZ
    The SIGXFSZ signal is sent to a process when it grows a file that exceeds the maximum allowed size.
SIGWINCH
    The SIGWINCH signal is sent to a process when its controlling terminal changes its size (a window change).[14]

Answer 2

Начиная с PHP 7.4, это теперь возможно, зарегистрировав обратный вызов обработчика с помощью sapi_windows_set_ctrl_handler функция.

Это дополняется sapi_windows_generate_ctrl_event, который можно использовать для отправки сигналов другим процессам, подключенным к той же консоли, что и вызывающий.

Только события CTRL-C и CTRL-BREAK могут обрабатываться в пространстве пользователя, события закрытия / выхода / завершения работы не могут быть реализованы безопасно, поскольку операционная система, вероятно, будет в непредсказуемом состоянии частичного завершения работы к моменту вызова функции обработчика, поэтому существует риск, что любой код, выполняемый на этом этапе, принесет больше вреда, чем пользы.

Вы можете найти дополнительную информацию о базовом механизме в MSDN:

• SetConsoleCtrlHandler()
• GenerateConsoleCtrlEvent()

PHP API почти идентичен базовому API C, единственное заметное отличие состоит в том, что PHP разрешает регистрацию только одного обратного вызова, и, следовательно, обработчик не имеет значимого возвращаемого значения, движок просто отмечает события как обработанные. Это сделано для упрощения реализации, поскольку стек функций может быть легко реализован в пользовательском пространстве, и аналогично, если вы не хотите обрабатывать событие, вы можете просто вызватьexit.

Answer 3

Если вы хотите запустить задачу в PHP через командную строку, которая занимает очень много времени, я постараюсь организовать ее по значкам и отслеживать, что уже сделано.

Теперь вы можете полностью обработать каждый значок (например, обработать, а затем сохранить его в XML-файле), а не только после обработки всего списка. Таким образом, сбой / остановка между ними приведет к отмене только одного значка, а не всех.

Если вы сохраняете свою текущую позицию после каждого значка, вы можете легко возобновить работу, когда ваш скрипт вылетает или останавливается.

Теперь, если вы проверите список процессов ОС, чтобы увидеть, запущен ли ваш скрипт, вы можете написать задание cron, которое запускает ваш скрипт каждые X минут, если он аварийно завершился и еще не работал.

Итак, TL;DR

• Процесс работы в маленьких значках
• Сохранение позиции последнего успешно обработанного значка
• Проверьте уже запущенный процесс при запуске
• Постоянно запускайте скрипт, пока все не будут довольны!

Кроме того, мне нравится PHP для небольших заданий командной строки, но если у вас такая большая задача, лучше подойдет что-то другое. Проверьте что-то, что может работать стабильно в течение длительного времени и имеет возможность показать его прогресс. Возможно, небольшое приложение на C# с минималистичным интерфейсом.