inetd doesn't work until stopped and restarted

Chris Faylor cgf@cygnus.com
Tue Jun 6 17:44:00 GMT 2000


On Tue, Jun 06, 2000 at 08:23:00PM -0400, Charles Wilson wrote:
>This probably has to do with the order in which Windows System services
>are started. e.g. if inetd depends on, say, 'windows socket services'(*)
>then if inetd is started at bootup *before* WSS, it'll fail. However,
>once the machine is running, then you can restart inetd and it'll work
>because WSS is up.
>
>I seem to remember some article in the Microsoft Knowledge Base about
>this, and how to resolve it -- but no specifics. Hunt around at
>support.microsoft.com.
>
>(*) 'WSS' is an imaginary service I made up. But you get the idea.

Chuck,
I've reinstalled my entire system twice and I still can't find this
WSS system that you say should be there.  Should I just type:

      mkdir WSS

to implement it?

I'm running Windows 96 with Internet Explorer 2.7 if that helps.

I'm pretty sure that WSS used to work fine on both linux and B20.1.

cgf
:-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-)

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com



More information about the Cygwin mailing list