X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Christopher McIntosh Subject: sshd via XP Service vs. sshd init daemon Date: Thu, 24 Nov 2005 21:18:58 -0600 Lines: 21 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-IsSubscribed: yes 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 Cyg-winners: I have a question that the FAQs do not seem to address. It is possible to install sshd as an init daemon (via usr/sbin/chkconfig --add) *and* it is also possible to install sshd as a full-fledged XP service (via /usr/bin/ssh-host-config). 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. Am I overlooking potential advantages for running as an independent, full-fledged service? Thanks to all who share the enlightenment! :) Christopher -- 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/