From: Gary <gary.mphelps@gmail.com>
To: Csaba Raduly <rcsaba@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: SSHD Issue Windows 2003 64 bit
Date: Wed, 10 Aug 2011 23:20:00 -0000 [thread overview]
Message-ID: <CAC8hJujKmNaUeuugv2Fm0840D6Ff7bEWh4MdQZ0mvTp_qs_5Cw@mail.gmail.com> (raw)
In-Reply-To: <CAC8hJugRX3Rp1GFngEjfw3sX0uGo1sj0cXSyGhJTBN1L3xChvw@mail.gmail.com>
http://cygwin.com/ml/cygwin/2008-02/msg00429.html (ignore the {})
On Wed, Aug 10, 2011 at 3:59 PM, Gary <gary.mphelps@gmail.com> wrote:
> The logs specify:
> /var/empty must be owned by root and not group or world-writable.
>
> I've tried changing permissions, and also looking on the forums for
> this {http://cygwin.com/ml/cygwin/2008-02/msg00429.html} I still can't
> figure it out. Let me know, thanks!
>
> On Tue, Aug 9, 2011 at 10:27 PM, Csaba Raduly <rcsaba@gmail.com> wrote:
>> On Tue, Aug 9, 2011 at 10:47 PM, Gary wrote:
>>> I'm having issues getting SSHD working on Windows Server 2003 64 bit.
>>> I've properly installed SSHD as a service but I receive the following
>>> error when starting the service from 'services.msc':
>>> 'The SSHD service on Local Computer started and then stopped. Some
>>> services stop automatically if they have no work to do, for example,
>>> The Performance Logs and Alerts service'.
>>>
>>> Also when I execute the following 'net start sshd' from the cygwin
>>> terminal I receive the following:
>>> 'The SSHD service is starting. The SSHD service could not be started.
>>> The service did not report an error'.
>>>
>>> Anything would help, thanks!
>>
>> You need to check the event log (application and/or system).
>>
>> Csaba
>> --
>> GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
>> The Tao of math: The numbers you can count are not the real numbers.
>> Life is complex, with real and imaginary parts.
>> "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
>> "People disagree with me. I just ignore them." -- Linus Torvalds
>>
>
>
>
> --
> Gary Phelps
>
--
Gary Phelps
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-08-10 23:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 20:48 Gary
2011-08-10 5:27 ` Csaba Raduly
2011-08-10 22:59 ` Gary
2011-08-10 23:20 ` Gary [this message]
2011-08-11 8:16 ` Thorsten Kampe
2011-08-11 16:41 ` Larry Hall (Cygwin)
2011-08-11 17:02 ` Gary
2011-08-11 17:34 ` Thorsten Kampe
2011-08-11 18:25 ` Gary
2011-08-11 18:54 ` Thorsten Kampe
2011-08-11 21:33 ` Gary
2011-08-11 23:20 ` Larry Hall (Cygwin)
2011-08-12 21:55 ` Gary
2011-08-15 21:11 ` Gary
2011-08-15 21:46 ` Larry Hall (Cygwin)
2011-08-15 23:11 ` Gary
2011-08-16 3:57 ` Larry Hall (Cygwin)
2011-08-16 22:25 ` Gary
2011-08-17 2:24 ` Larry Hall (Cygwin)
2011-08-19 21:53 ` Gary
2011-08-22 15:15 ` Larry Hall (Cygwin)
2011-08-22 17:12 ` Gary
2011-08-22 20:39 ` Larry Hall (Cygwin)
2011-08-23 18:55 ` Gary
2011-08-24 2:35 ` Larry Hall (Cygwin)
2011-08-19 21:59 ` Gary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAC8hJujKmNaUeuugv2Fm0840D6Ff7bEWh4MdQZ0mvTp_qs_5Cw@mail.gmail.com \
--to=gary.mphelps@gmail.com \
--cc=cygwin@cygwin.com \
--cc=gphelps@ucmerced.edu \
--cc=rcsaba@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).