From owner-freebsd-hackers Sat Oct 10 19:31:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00200 for freebsd-hackers-outgoing; Sat, 10 Oct 1998 19:31:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hotjobs.com (fs3.ny.genx.net [206.64.4.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA00192 for ; Sat, 10 Oct 1998 19:31:13 -0700 (PDT) (envelope-from perlsta@hotjobs.com) Received: (qmail 7489 invoked by uid 1288); 11 Oct 1998 02:29:12 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 11 Oct 1998 02:29:12 -0000 Date: Sat, 10 Oct 1998 22:29:12 -0400 (EDT) From: Alfred X-Sender: perlsta@fs3.ny.genx.net To: hackers@FreeBSD.ORG Subject: question about the xsocket struct. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG is it safe to use the: uid_t so_uid; /* XXX */ in an xsocket as defined in: i'm concered about the /* XXX */ near it as the user id associated with the socket? if not, anyone have an idea how to get that info from a "struct xtcpbc" (the user id associated with the socket?) thanks, Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message