* "D�hr, Markus ICC-H" wrote:
> > The naive approach (reconfigure XServer service, start it,
> > see what happens) results in error 18666, "user missing
> > privilege".
>
> I think the users need the following priviledges:
>
> - start as a batch job
> - start as service
> - allow to replace token on processlevel
That doesn't work either. The same error message is logged.
I've tried it on the command line. Run as Administrator, serv.exe
listens on various sockets and seems happy. Run as another user it
fails differently:
18597 ERROR: Error on opening semaphore:
'Global\SAP DBTech-XSERVER-', rc = 161
If 161 is a Win32 error code, it's ERROR_BAD_PATHNAME, which does
not mean "object not found". I suspect it doesn't like the prefix
"Global\" when run from a TS session.
Run from the console, starting the XServer on the command line
works, starting the service doesn't. That's probably still the
failing group lookup, which may not be done when running from the
command line. That's all conjecture, though.
What do I have to do to make it work? If all else fails, I'm going
to try to build it from source, put lots of debug output in and see
for myself exactly what happens. I don't really like doing that,
though.
--
Christian Ullrich Registrierter Linux-User #125183
"There's nothing we can't face -- except for Bun-bun..."
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
