Greetings Rick,
Rick McGuire wrote:
Note that with this new setup, a user will be able to run multiple releases if
they wish or even use both the 32- and 64- bit versions at the same time.
Oh wow!!! This is super good news.
Once you have a solid looking version checked into the source
> On 27 Nov 2018, at 23:49, Rick McGuire wrote:
>
> This new setup does not require a pid file.
Sorry… I just did a cut and paste from a snippet used for testing.
And used the wrong terminology
You just need a token to serve as anchor point for a local connection
The way zeromq and
On Tue, Nov 27, 2018 at 5:37 PM Enrico Sorichetti via Oorexx-devel <
oorexx-devel@lists.sourceforge.net> wrote:
>
>
> > On 27 Nov 2018, at 22:33, Rick McGuire wrote:
> >
> …
> …
> ...
> > Do this make sense? Can the "~" form be used on the bind?
> >
>
> NO the ~ is resolved by the shell
>
> IMO
> On 27 Nov 2018, at 22:33, Rick McGuire wrote:
>
…
…
...
> Do this make sense? Can the "~" form be used on the bind?
>
NO the ~ is resolved by the shell
IMO the best place would be a hidden file in the home dir
Which can be dynamically built using something like
#include
#include
I'm reworking the rxapi daemon process to no longer use AF_INET sockets for
IPC but rather use AF_LOCAL sockets. The new daemon processes will be
specific to the user and bind to a user-specific name so that there will be
one daemon per Rexx-using user.
The service names have to be bound into the
