From jeffs@kant.ee.washington.edu Sun Jun 18 17:44:01 2000 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA37324 for ; Sun, 18 Jun 2000 17:44:01 -0700 Received: from kant.ee.washington.edu (kant.ee.washington.edu [128.95.205.15]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA32436 for ; Sun, 18 Jun 2000 17:44:00 -0700 Received: from spinoza.ee.washington.edu (spinoza.ee.washington.edu [128.95.205.3]) by kant.ee.washington.edu (8.9.3/RCS-2.1) with ESMTP id RAA12666 for ; Sun, 18 Jun 2000 17:31:14 -0700 (PDT) Date: Sun, 18 Jun 2000 17:40:31 -0700 (PDT) From: Jeff Silverman X-Sender: jeffs@spinoza.ee.washington.edu To: UW Linux Group Subject: Re: Starting SSH services In-Reply-To: <003901bfd8ce$d5d79040$30be1ad0@cs.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In general, there are two ways to start a daemon. A "stand alone" daemon is started from (depending on your version of UNIX, and Linux is a UNIX) /etc/init.d or /etc/rc.d/init.d and /etc/rc.d/rcX.d . I don't remember the proper name for the other kind of daemon, but it is started from inetd, which is a "super daemon" that starts other daemons. inetd is configured in /etc/inetd.conf. The advantage of a stand alone daemon is that, since it only has to start once, it responds to initial requests faster. The advantages of a daemon started by inetd is that there is better security, if you change the daemon configuration, those changes manifest themselves immediately (because the configuration file is read at startup), and if the daemon crashes for some reason, it will restart at the next inbound connection. Some daemons will not run under inetd - named and httpd come to mind. Some daemons should be run stand alone - rshd comes to mind (although some would argue that rshd shouldn't be run at all) As a sysadmin, you have to make policy decisions about whether 'tis better to have a highly secure system, an easy to use system, a fast system, or a simple system. It is hard to acheive all of these, but it is easy to fail all of them. Jeff Silverman, sysadmin for the Research Computing Systems (RCS) University of Washington, School of Engineering, Electrical Engineering Dept. Box 352500, Seattle, WA, 98125-2500 jeffs@isdl.ee.washington.edu http://rcs.ee.washington.edu/BRL/people/jeffs/ On Sat, 17 Jun 2000, Ryan Hennig wrote: > I've just installed the openssh packages on a webserver, and now I am trying > to figure out how to start the sshd service so that I can login with ssh. I > have scoured the openssh.com site, and all of their install instructions > stop after the sshd program is installed, with no mention of how to get the > thing to start accepting ssh logins (and also restart after a reboot). > > I am very new to linux system administration, so perhaps somebody could also > point me to some tutorial on starting and managing services in linux, or > some other good sysadmin tutorial. > > Thanks. > > Ryan Hennig > ACM Student Webmaster > Dept. of Computer Science and Engineering > University of Washington > > > .