Would installing the service under the user account help solve this particular
problem
(https://docs.microsoft.com/en-us/windows/desktop/ad/setting-up-a-serviceampaposs-user-account)?
Or should the service option be removed?
—-rony
Rony G. Flatscher (mobil/e)
> Am 26.07.2018 um 18:34 schrieb
Up through 3.2, rxapi used shared memory for interprocess communications
with no user isolation at all. With 4.0, this was changed to the current
setup using sockets and user-level isolation.
There's no real work around for this and there's no plan to support cross
user communications in the
We have an open bug report https://sourceforge.net/p/oorexx/bugs/1321/
It seems that the user is trying to access a named RexxQueue from different
Windows users: the local user, and a Windows Service running under the
special Windows account LocalService.
Do I correctly understand that today
