| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Johan De Meersman | Date: | November 25 2010 8:28am |
| Subject: | Re: localhost vs domain for connection string | ||
| View as plain text | |||
On Wed, Nov 24, 2010 at 4:44 PM, Jerry Schwartz <jerry@stripped> wrote: > [JS] This might or might not be enabled by default. I'm running on Windows, > and I seem to remember having to change it. > > # Enable named pipe, bypassing the network stack > enable-named-pipe > Windows' named pipes are not the same as unix sockets, although the general idea is similar. I'm not sure, but I think the Unix socket file is always created. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
| Thread | ||
|---|---|---|
| • localhost vs domain for connection string | Brent Clark | 23 Nov |
| • Re: localhost vs domain for connection string | Johan De Meersman | 23 Nov |
| • RE: localhost vs domain for connection string | Jerry Schwartz | 23 Nov |
| • Re: localhost vs domain for connection string | Johan De Meersman | 24 Nov |
| • RE: localhost vs domain for connection string | Jerry Schwartz | 24 Nov |
| • Re: localhost vs domain for connection string | Johan De Meersman | 25 Nov |
| • RE: localhost vs domain for connection string | Jerry Schwartz | 29 Nov |
| • Re: localhost vs domain for connection string | Jan Steinman | 23 Nov |
