Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • CLI Reference

    Home FortiWeb 6.3.3 CLI Reference
    6.3.3
    7.6.1
    7.6.0
    7.4.5
    7.4.4
    7.4.3
    7.4.2
    7.4.1
    7.4.0
    7.2.10
    7.2.9
    7.2.8
    7.2.7
    7.2.6
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.0.9
    7.0.8
    7.0.7
    7.0.6
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.4.3
    6.4.2
    6.4.1
    6.4.0
    6.3.23
    6.3.19
    6.3.18
    6.3.17
    6.3.16
    6.3.15
    6.3.14
    6.3.13
    6.3.11
    6.3.10
    6.3.9
    6.3.7
    6.3.6
    6.3.5
    6.3.4
    6.3.3
    6.3.2
    6.3.1
    6.3.0
    6.2.6
    6.2.5
    6.2.4
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.1.2
    6.1.1
    5.7.0
    5.6.1
    5.6.0

    system kill

    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

    Previous
    Next

    system kill

    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

    Previous
    Next