Builder tcpdump-solaris10-amd64 Build #6129

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-tcpdump-solaris10-amd64' triggered this build

Steps and Logfiles:

1. git update ( 7 secs )
   1. stdio
2. shell Set developer mode ( 0 secs )
   1. stdio
3. shell_1 './autogen.sh' ( 7 secs )
   1. stdio
4. shell_2 configure ( 1 mins, 31 secs )
   1. stdio
5. shell_3 gmake ( 6 mins, 42 secs )
   1. stdio
6. shell_4 check ( 2 mins, 46 secs )
   1. stdio
   2. failure-outputs.txt

Build Properties:

Forced Build Properties:

Responsible Users:

1. Julia Evans

   juliaohnoyoudont@jvns.ca

Timing:

All Changes:

:

1. Change #260204

   Category	tcpdump
   Changed by	Julia Evans <juliaohnoyoudont@jvns.ca>
   Changed at	Sat 07 Mar 2026 14:43:55
   Repository	https://git.tcpdump.org/tcpdump
   Project	tcpdump
   Branch	master
   Revision	3f4e00b98b4d73e51cf8f024f4ad2b5ce3c2423a

   Comments

   tcpdump(1): rewrite examples section [skip ci]
   The goal here is to make the examples section much more useful to
   beginners or very occasional users of tcpdump.
   
   Replace the current EXAMPLES section with:
   
   - 3 examples explaining important flags (-n, -i, and -w, -#)
   - 4 very basic examples showing different features of the pcap language
     (filtering by host, protocol, and port, and using "and")
   - 2 "advanced" examples from the previous EXAMPLES section to show how
     powerful tcpdump is
   
   Remove all hostnames and references to UC Berkeley's network ("snup",
   "helios", "ucb-ether", etc), which most tcpdump users are likely not
   familiar with. It's not totally clear that "snup" is intended to be
   the name of a network resource and not an obscure pcap-filter keyword.
   
   Always use -n to reiterate that -n is an important flag.

   Changed files

   • tcpdump.1.in