Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!math.fu-berlin.de!opal!gmdtub!prosun!tmh
From: tmh@prosun.first.gmd.de (Thomas Hoberg)
Newsgroups: comp.unix.sysv386
Subject: Re: Rebooting Sys V/386
Keywords: shutdown reboot autoboot
Message-ID: <563@bigfoot.first.gmd.de>
Date: 28 Mar 91 00:01:13 GMT
References: <419@srs.UUCP>
Sender: news@bigfoot.first.gmd.de
Reply-To: tmh@prosun.first.gmd.de (Thomas Hoberg)
Organization: GMD-FIRST, D-1000 Berlin 10
Lines: 21

In article <419@srs.UUCP>, dlucy@srs.UUCP (Doug Lucy) writes:
|> Is there a way to force a sys V/386 3.2 system to reboot?
|> I need to cause a reboot from a remote login after changing
|> the kernel with idbuild. Is there a way to do this with
|> just shutdown? Can it be done with a call to reset the system?
|> 
/etc/uadmin won't help there, because it only works from the console. However
the system call should work. It takes two arguments (command + function), which
are defined in /usr/include/sys/uadmin.h. Not having the documentation at hand
I guess it should be uadmin(A_SHUTDOWN, AD_BOOT) for you.
Should the new kernel and configuration fail to reach init level 3, you are out
in the cold, but I guess you know that...

-- tom
----
Thomas M. Hoberg   | UUCP: tmh@bigfoot.first.gmd.de  or  tmh%gmdtub@tub.UUCP
c/o GMD Berlin     |       ...!unido!tub!gmdtub!tmh (Europe) or
D-1000 Berlin 12   |       ...!unido!tub!tmh
Hardenbergplatz 2  |       ...!pyramid!tub!tmh (World)
Germany            | BITNET: tmh%DB0TUI6.BITNET@DB0TUI11 or
+49-30-254 99 160  |         tmh@tub.BITNET