Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ncar!gatech!udel!haven!umd5!lewhoosh.umd.edu!matthews
From: matthews@lewhoosh.umd.edu (Mike Matthews)
Newsgroups: comp.sys.next
Subject: Re: IRC on NeXT
Message-ID: <7930@umd5.umd.edu>
Date: 30 Jan 91 17:08:10 GMT
References: <910029.092207.sig@SCrossland> <7923@umd5.umd.edu> <1253@toaster.SFSU.EDU>
Sender: news@umd5.umd.edu
Organization: Computer Science Center, University of Maryland, College Park
Lines: 24

In article <1253@toaster.SFSU.EDU> eps@cs.SFSU.EDU (Eric P. Scott) writes:
>I prefer
>	echo exec /usr/local/irc/ircd|su -f daemon &

>There's no good reason for ircd to run as root, and I won't
>certify that it won't misbehave if you let it.

>					-=EPS=-

Or you can have its setuid-on-execute bit set.

I created a 'dummy' user irc, and have all of the files owned by it.  I also
made a group irc, so the person who really does all of the ircd handling can
install and fix and whatnot the files without becoming root.  Now he just
su's into irc, but before we didn't have it set up that way.

Either way, the same thing happens.

(Currently, lewhoosh's ircd is down again, for unknown reasons; it just kind
of quit)
------
Mike Matthews, matthews@lewhoosh.umd.edu (NeXT)/matthews@umdd (bitnet)
------
When you do not know what you are doing, do it neatly.