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 Reply-To: Cygwin List Message-Id: <6.2.0.14.0.20050218193133.02fdb990@pop.prospeed.net> Date: Fri, 18 Feb 2005 19:33:49 -0500 To: cygwin AT cygwin DOT com From: Larry Hall Subject: Re: Service not starting unless... In-Reply-To: <42168022.5080802@schoenhaber.de> References: <2F8AC1EEE4082E468DD2A31D63E1E48E0BA07490 AT ryan DOT na DOT ds DOT ussco DOT com> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20050218145943 DOT 02fdb990 AT pop DOT prospeed DOT net> <42168022 DOT 5080802 AT schoenhaber DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 06:54 PM 2/18/2005, you wrote: >Larry Hall wrote: >> If you allow the service to interact with the desktop, the implication is >> that it wants to run something that would be visual on your desktop. It >> also has the disadvantage that the service will terminate when the desktop >> is closed (i.e. you log out), which is not usually what people expect from >> a service. >> >Allowing a service to interact with the desktop doesn't necessarily mean >that it will be terminated when when the user logs out. Seems I can't reproduce that behavior now either, at least with sshd. So this isn't a golden rule. ;-) >OTOH I don't understand what the "Cygwin service" is, the OP refers to. >It might be the exception that really terminates on user log-off. Right. That's why I pointed the OP to: >Problem reports: http://cygwin.com/problems.html first in my original reply. Oops! I did it again. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/