X-Spam-Check-By: sourceware.org Message-ID: <438688E2.D518081C@dessent.net> Date: Thu, 24 Nov 2005 19:45:38 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: sshd via XP Service vs. sshd init daemon References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Christopher McIntosh wrote: > QUERY: What are the pros and cons of each method? > > IMO, I prefer to have less full-fledged services; then it is simpler to > start several daemons (e.g., xinetd, sshd, ftpd, ...) via a single 'net > start init' or 'cygrunsrv --start init' reducing the number of tasks to > perform for a change in state. I know that sshd has support for being run from inetd, but it is very old, very inefficient, not very well tested, lacks some features, and is generally frowned upon. Remember that a host key has to be generated each time sshd starts and this can take some time, so doing that for every connection is just silly. In the context of Cygwin, it should work as long as sshd runs as SYSTEM and the permissions on the host keys, config files, /var/empty directory (etc) are correct. And I would not expect to ever have both working at the same time (daemon and inetd) unless you installed a second copy of sshd into a different --prefix that had its own host keys and everything else. I'm not sure why you would ever want this though, or maybe I'm misinterpreting your question. In short, stay away from inetd. That's my advice. Starting and stopping is trivial: "for F in sshd cron cygserver; do cygrunsrv -S $F; done". Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/