Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!orion.oac.uci.edu!hardy From: hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) Newsgroups: comp.sys.next Subject: Re: Standalone configuration ????? Message-ID: Date: 13 Apr 91 15:36:22 GMT References: <402@aplcomm.JHUAPL.EDU> Organization: U.C.Irvine, Dept. of Physics Lines: 30 Nntp-Posting-Host: golem.ps.uci.edu In-reply-to: derek@stdb.jhuapl.edu's message of 12 Apr 91 17:48:57 GMT In article <402@aplcomm.JHUAPL.EDU> derek@stdb.jhuapl.edu (Derek at SFA) writes: > I have an 030 Next at home that I use for almost everything except networking > and printing(No printer yet). I was wondering if any one knew of what to disable > in the rc files so that certain daemons won't get started. What is not needed? I tried this but found that if you are not careful, the system will not boot. My remedy: a script (suid root) which will kill the 4 biod processes and sendmail (you can add your choice of others) after booting: kill_proc: #! /bin/sh -u PIDS=`ps -ax | bm sendmail | grep -v bm | awk '{print $1}'` kill -TERM $PIDS PIDS=`ps -ax | bm autonfsmount | grep -v bm | awk '{print $1}'` kill -TERM $PIDS PIDS=`ps -ax | bm inetd | grep -v bm | awk '{print $1}'` kill -TERM $PIDS PIDS=`ps -ax | bm biod | grep -v bm | awk '{print $1}'` kill -TERM $PIDS Not elegant, but works -- and if you carry your slab to the office you cna hook it up to the net without rewriting rc. Greetings, Hardy -------****------- Meinhard E. Mayer (Hardy); Department of Physics, University of California Irvine CA 92717; (714) 856 5543; hardy@golem.ps.uci.edu or MMAYER@UCI.BITNET