Software: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16. PHP/5.4.16 

uname -a: Linux roko-bkp 3.10.0-1160.102.1.el7.x86_64 #1 SMP Tue Oct 17 15:42:21 UTC 2023 x86_64 

uid=48(apache) gid=48(apache) groups=48(apache),1003(webmaster) 

Safe-mode: OFF (not secure)

/usr/share/doc/sudo-1.8.23/examples/   drwxr-xr-x
Free 8.92 GB of 93.48 GB (9.55%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     syslog.conf (1.05 KB)      -rw-r--r--

# This is a sample syslog.conf fragment for use with Sudo.
#
# By default, sudo logs to "authpriv" if your system supports it, else it
# uses "auth".  The facility can be set via the --with-logfac configure
# option or in the sudoers file.
# To see what syslog facility a sudo binary uses, run `sudo -V' as *root*.
#
# NOTES:
#	The whitespace in the following line is made up of <TAB>
#       characters, *not* spaces.  You cannot just cut and paste!
#
#	If you edit syslog.conf you need to send syslogd a HUP signal.
#	Ie: kill -HUP process_id
#
#	Syslogd will not create new log files for you, you must first
#	create the file before syslogd will log to it.  Eg.
#	'touch /var/log/sudo'

# This logs successful and failed sudo attempts to the file /var/log/auth
# If your system has the authpriv syslog facility, use authpriv.debug
auth.debug					/var/log/auth

# To log to a remote machine, use something like the following,
# where "loghost" is the name of the remote machine.
# If your system has the authpriv syslog facility, use authpriv.debug
auth.debug					@loghost