From owner-freebsd-hackers  Mon Mar 17 19:27:58 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA27443
          for hackers-outgoing; Mon, 17 Mar 1997 19:27:58 -0800 (PST)
Received: from kithrup.com (kithrup.com [205.179.156.40])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA27438
          for <hackers@freebsd.org>; Mon, 17 Mar 1997 19:27:55 -0800 (PST)
Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id TAA15908 for hackers@freebsd.org; Mon, 17 Mar 1997 19:27:52 -0800
Date: Mon, 17 Mar 1997 19:27:52 -0800
From: Sean Eric Fagan <sef@Kithrup.COM>
Message-Id: <199703180327.TAA15908@kithrup.com>
To: hackers@freebsd.org
Subject: A really minor annoyance
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

2.2-GAMMA has

	while ((so->so_state & SS_ISCONNECTING) && so->so_error == 0) {
		error = tsleep((caddr_t)&so->so_timeo, PSOCK | PCATCH,
			"connec", 0);

in kern/uipc_syscalls.c.  Thus, "connec" shows up if you do a control-T (or
whatever you have status set to) while something is waiting there.

"connec" is *really* annoying.  Why isn't it "connect"?  It used to be
either "netcon" or "connect" -- "connec" is worse than "netcon" (because it
looks like a typo), and "connect" is certainly better than "connec" as well.
(And since it is in the system call connect, having it say "connect" makes
sense as well.  But even "netcon" is better.)

It's not because of the number of characters -- "running" (what you get when
a process is active) has just as many characters as "connect".

Sean.