Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

CLI Reference

system kill

Use this command to terminate a process currently running on FortiWeb, or send another signal from the FortiWeb OS to the process.

To use this command, your administrator account’s access control profile must have either w or rw permission to the mntgrp area. For details, see Permissions.

Syntax

diagnose system kill <signal_int> <pid_int>

Variable Description Default

<signal_int>

Enter the ID of the signal to send to the process. This in an integer between 1 and 32. Some common signals are:

  • 1—Varies by the process’s interpretation, such as re-read configuration files or re-initialize (hang up; SIGHUP).

    For example, the FortiWeb web UI verifies its configuration files, then restarts gracefully.

  • 2—Request termination by simulating the pressing of the interrupt keys, such as Ctrl + C (interrupt; SIGINT).

  • 3—Force termination immediately and do a core dump (quit; SIGQUIT).

  • 9—Force termination immediately (kill; SIGKILL).

  • 15—Request termination by inter-process communication (terminate; SIGTERM).

  • 43—Request to activate or deactivate the jemallc profile. If you run it the first time, jemallc profile is activated. Running the same command again will deactivate the jemallc profile. The following <pid_int> should be defined with the pid of the proxyd.
    Considering jemalloc profile has a big impact on the system performance, it's recommended to deactivate it after jemalloc profile debug.

No default.

<pid_int>

Enter the process ID where the signal is sent to.

To list all current process IDs, use system top .

No default.

Related topics

system kill

Use this command to terminate a process currently running on FortiWeb, or send another signal from the FortiWeb OS to the process.

To use this command, your administrator account’s access control profile must have either w or rw permission to the mntgrp area. For details, see Permissions.

Syntax

diagnose system kill <signal_int> <pid_int>

Variable Description Default

<signal_int>

Enter the ID of the signal to send to the process. This in an integer between 1 and 32. Some common signals are:

  • 1—Varies by the process’s interpretation, such as re-read configuration files or re-initialize (hang up; SIGHUP).

    For example, the FortiWeb web UI verifies its configuration files, then restarts gracefully.

  • 2—Request termination by simulating the pressing of the interrupt keys, such as Ctrl + C (interrupt; SIGINT).

  • 3—Force termination immediately and do a core dump (quit; SIGQUIT).

  • 9—Force termination immediately (kill; SIGKILL).

  • 15—Request termination by inter-process communication (terminate; SIGTERM).

  • 43—Request to activate or deactivate the jemallc profile. If you run it the first time, jemallc profile is activated. Running the same command again will deactivate the jemallc profile. The following <pid_int> should be defined with the pid of the proxyd.
    Considering jemalloc profile has a big impact on the system performance, it's recommended to deactivate it after jemalloc profile debug.

No default.

<pid_int>

Enter the process ID where the signal is sent to.

To list all current process IDs, use system top .

No default.

Related topics