LinuxCommandLibrary

trip

Trace route packets take to network hosts

TLDR

Basic usage with default parameters

$ sudo trip [example.com]
copy

Trace without requiring elevated privileges (supported platforms only)
$ trip [example.com] --unprivileged
copy

Trace using IPv6 only
$ sudo trip [example.com] --ipv6
copy

Trace using the udp protocol
$ sudo trip [example.com] --protocol [udp]
copy

Use custom destination port 443 for tcp tracing
$ sudo trip [example.com] --protocol [tcp] --target-port [443]
copy

Use custom source port 5000 for udp tracing
$ sudo trip [example.com] --protocol [udp] --source-port [5000]
copy

SYNOPSIS

trip

DESCRIPTION

The trip command displays the amount of time that has elapsed since the last system boot. It is a simple utility providing a quick way to determine system uptime. The output typically includes the number of days and hours since the system was last restarted. The command is most commonly used to get an indication of system stability, assess the impact of reboots, or to determine how long a system has been operational without intervention. It's often used in scripts or monitoring systems to track server uptime and availability. The command is part of the procps package and relies on information from the /proc filesystem, specifically /proc/uptime. The result of the trip command is the same as if you run uptime and parse the result.

CAVEATS

The accuracy of the output depends on the accuracy of the system clock. Major clock discrepancies can affect the reported uptime. trip relies on the /proc filesystem, which might not be available on all systems.

RETURN VALUE

The trip command returns 0 on success. Any other return value means that there was an error.

FILES

/proc/uptime file is being read to determine the uptime.

SEE ALSO

uptime(1), w(1), top(1), ps(1)

Copied to clipboard