Sudo Log Client Manual
send sudo I/O log to log
sudo_sendlog can be used to send the
sudoers I/O log path
to a remote log server such as sudo_logsrvd(8) for central storage.
The options are as follows:
- Only send the accept event, not the I/O associated with the log. This can be used to test the logging of accept events without any associated I/O.
- The path to a certificate authority bundle file, in PEM format, to use instead of the system's default certificate authority database when authenticating the log server. The default is to use the system's default certificate authority database.
- The path to the client's certificate file in PEM format. This setting is required when the connection to the remote log server is secured with TLS.
- Display a short help message to the standard output and exit.
- Connect to the specified host instead of localhost.
- Use the specified iolog-id when restarting a log
transfer. The iolog-id is reported by the server
when it creates the remote I/O log. This option may only be used in
conjunction with the
- The path to the client's private key file in PEM format. This setting is required when the connection to the remote log server is secured with TLS.
- If specified, the server's certificate will not be verified during the TLS
handshake. By default,
sudo_sendlogverifies that the server's certificate is valid and that it contains either the server's host name or its IP address. This setting is only supported when the connection to the remote log server is secured with TLS.
- Use the specified network port when connecting to the log server instead of the default, port 30344.
- Restart an interrupted connection to the log server. The specified
restart-point is used to tell the server the point
in time at which to continue the log. The
restart-point is specified in the form
“seconds,nanoseconds” and is usually the last commit point
received from the server. The
-ioption must also be specified when restarting a transfer.
- Send a reject event for the command using the specified reject-reason, even though it was actually accepted locally. This can be used to test the logging of reject events; no I/O will be sent.
- Stop sending log records and close the connection when
stop-point is reached. This can be used for testing
purposes to send a partial I/O log to the server. Partial logs can be
restarted using the
-roption. The stop-point is an elapsed time specified in the form “seconds,nanoseconds”.
- Open number simultaneous connections to the log server and send the specified I/O log file on each one. This option is useful for performance testing.
- Print the
sudo_sendlogversion and exit.
sudo_sendlog supports a flexible debugging
framework that is configured via
lines in the sudo.conf(5) file.
For more information on configuring sudo.conf(5), refer to its manual.
- Sudo front-end configuration
Many people have worked on
sudo over the
years; this version consists of code written primarily by:
See the CONTRIBUTORS.md file in the
distribution (https://www.sudo.ws/about/contributors/) for an exhaustive
list of people who have contributed to
If you believe you have found a bug in
sudo_sendlog, you can submit a bug report at
Limited free support is available via the sudo-users mailing list, see https://www.sudo.ws/mailman/listinfo/sudo-users to subscribe or search the archives.
sudo_sendlog is provided “AS
IS” and any express or implied warranties, including, but not limited
to, the implied warranties of merchantability and fitness for a particular
purpose are disclaimed. See the LICENSE.md file distributed with
sudo or https://www.sudo.ws/about/license/ for