>>      o fix shared memory on Win2k terminal server
>>      We might be able to just mark this as not supported.
>I have attached a patch that I think fixes this. The problem I saw 
>and fixed is, that the shmem created in a terminal services 
>client is not 
>visible to the console (or services.msc).

Does this actually fix the problem for you?
Because, as I have previously posted I think, it does *not* solve the
problem on any of my test machines. I still get the shmget() error
message when running from a TS session.
(Yes, I tried specifically with your patch, since I thought maybe I got
something wrong before)

I'm on Windows 2000 Server, tested both DC and non-DC machines. What are
you testing on?

Also, I don't really see how the visibility of the shmem segment
matters. We can't *create* the first instance of it, which should not
affect this at all. And if we passed that, all backends are still
execute in the same session, so there is no effect on it.

services.msc only interacts with the SCM, it has nothing at all to do
with shmem.


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Reply via email to