From owner-freebsd-hackers  Sun Oct 29 14:45:51 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id OAA22496
          for hackers-outgoing; Sun, 29 Oct 1995 14:45:51 -0800
Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA22491
          for <freebsd-hackers@freebsd.org>; Sun, 29 Oct 1995 14:45:48 -0800
Received: (from henrich@localhost) by crh.cl.msu.edu (8.6.12/8.6.12) id RAA05648 for freebsd-hackers@freebsd.org; Sun, 29 Oct 1995 17:45:54 -0500
From: Charles Henrich <henrich@crh.cl.msu.edu>
Message-Id: <199510292245.RAA05648@crh.cl.msu.edu>
Subject: Why cant a setuid process do a shutdown?
To: freebsd-hackers@freebsd.org
Date: Sun, 29 Oct 1995 17:45:54 -0500 (EST)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 624       
Sender: owner-hackers@freebsd.org
Precedence: bulk

Okay, I've tried everything, and I cant figure out anyway in which a setuid
process can execute a shutdown.

The shutdown will proceed as normal, but when the final time has come to kill
init, nothing happens.  Right before that point all logged in connections are
nuked, getty is killed, (shells logged into the console still are active
however).  I've manually forced both my uid and euid and guid and geuid are all
zero's.  but the system("shutdown"); fails..  anyone have any ideas?

-Crh

    Charles Henrich     Michigan State University     henrich@crh.cl.msu.edu

                     http://rs560.msu.edu/~henrich/