From owner-freebsd-current  Sun Nov 16 09:44:25 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA02247
          for current-outgoing; Sun, 16 Nov 1997 09:44:25 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA02239
          for <freebsd-current@freebsd.org>; Sun, 16 Nov 1997 09:44:18 -0800 (PST)
          (envelope-from evanc@synapse.net)
Received: (qmail 18666 invoked from network); 16 Nov 1997 17:44:11 -0000
Received: from cello.synapse.net (199.84.54.81)
  by conductor.synapse.net with SMTP; 16 Nov 1997 17:44:11 -0000
Date: Sun, 16 Nov 1997 12:44:10 -0500 (EST)
From: Evan Champion <evanc@synapse.net>
To: freebsd-current@freebsd.org
Subject: Which setuid's don't work?
Message-ID: <Pine.BSF.3.96.971116123732.5729C-100000@cello.synapse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Are any of the get/setuid functions ie:

setuid
seteuid
setreuid

(and their get/gid combinations) still not working properly in 3.0-current
(and I suppose 2.2* as well)? 

I'm wondering because the perl5 hints still have seteuid() disabled, even
though it seems to work fine in my Kerberos 5 ksu.

Evan