- GRAYBYTE UNDETECTABLE CODES -

403Webshell
Server IP : 184.154.167.98  /  Your IP : 3.21.247.221
Web Server : Apache
System : Linux pink.dnsnetservice.com 4.18.0-553.22.1.lve.1.el8.x86_64 #1 SMP Tue Oct 8 15:52:54 UTC 2024 x86_64
User : puertode ( 1767)
PHP Version : 7.2.34
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : ON  |  Sudo : ON  |  Pkexec : ON
Directory :  /etc/sysconfig/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /etc/sysconfig/pmlogger.rpmnew
# Environment variables for the primary pmlogger daemon.  See also
# the pmlogger control file and pmlogconf(1) for additional details.
# Also see separate pmlogger_farm configuration for the non-primary
# logger configuration settings, separate to this file.
# Settings defined in this file will override any settings in the
# pmlogger zeroconf file (if present).

# Behaviour regarding listening on external-facing interfaces;
# unset PMLOGGER_LOCAL to allow connections from remote hosts.
# A value of 0 permits remote connections, 1 permits local only.
PMLOGGER_LOCAL=1

# Max length to which the queue of pending connections may grow
# A value of 5 is the default.
# PMLOGGER_MAXPENDING=5

# Default sampling interval pmlogger uses when no more specific
# interval is requested.  A value of 60 seconds is the default.
# Both pmlogger command line (via control file) and also pmlogger
# configuration file directives will override this value.
# PMLOGGER_INTERVAL=60

# The default behaviour, when pmlogger configuration comes from
# pmlogconf(1), is to regenerate the configuration file and check for
# changes whenever pmlogger is started from pmlogger_check(1).
# If the PMDA configuration is stable, this is not necessary, and
# setting PMLOGGER_CHECK_SKIP_LOGCONF to yes disables the regeneration
# and checking.
# PMLOGGER_CHECK_SKIP_LOGCONF=yes

Youez - 2016 - github.com/yon3zu
LinuXploit