my understanding was that all instances connect to a running daemon and have separated user spaces in it. Running separate processes would be possible only when making the interpreter instances connect to different ports.
When testing the s390x port at a an IBM (Marist) Linux VM that I could not control the firewall on, I found that instead of stopping, everything just got really slow with for example a ridiculously low CPS score and socket timeouts on ordinary things - not always the things we associate with rxapi like queues and other ipc. This was remedied when the firewall was opened - but it was not an obvious error. In this case, rxapi could connect but the interpreter instance could not use it - I think. Thanks for your email, it re-triggered my earlier idea to work on a docker image that will virtualize the lot, so I can rerun P.O.’s tests all on one machine and make comparisons. René > On 21 Nov 2018, at 15:14, CV Bruce <cvbr...@gmail.com> wrote: > > I may not have been entirely accurate. I believe that two rxapi process can > run at the same time as long as they have different PID files. The problem > is that only one of them can bind the socket. Do we know if rxapi issues an > error message if it can not bind the socket? If so where does it send the > error message? > > Bruce >> On Nov 21, 2018, at 8:21 AM, CV Bruce <cvbr...@gmail.com >> <mailto:cvbr...@gmail.com>> wrote: >> >> Enrico, >> >> I’m a little concerned that installing anything in ~/… will make it user >> specific, and not system wide. Since only one copy of rxapi can run at a >> time, then only one user can use ooRexx. In your explorations can you test >> for this? >> >> "The main difference [on Mac OS] is that an agent is run on behalf of the >> logged in user while a daemon runs on behalf of the root user or any user >> you specify with the UserName key.” >> >> This may imply that if you log off the daemon may stop running, or the >> daemon may not start until the user logs on. >> >> Yours, >> >> Bruce >> >>> On Nov 21, 2018, at 8:03 AM, Enrico Sorichetti via Oorexx-devel >>> <oorexx-devel@lists.sourceforge.net >>> <mailto:oorexx-devel@lists.sourceforge.net>> wrote: >>> >>> >>> >>>> On 21 Nov 2018, at 15:23, Rick McGuire <object.r...@gmail.com >>>> <mailto:object.r...@gmail.com>> wrote: >>>> >>>> I believe writing the pid file at that location is part of the >>>> requirements for running as a daemon on other unix-based systems. >>> >>> >>> Does not seem true for Mac OS >>> >>> I have been running and ooRexx-ing for a while with /tmp/ooRexx.pid >>> and everything seems too work >>> >>> Anyway I will keep experimenting with the different setups >>> >>> also, on Mac OS there are the Agents and the Daemons >>> >>> And the plist for starting an agent can be in ~/Library/LaunchAgents >>> >>> So again no need to sudo anything, >>> But I will have to check what happens when alternating logins with >>> different users >>> Without logging off >>> >>> I just looked and home-brew does not need sudo because it assumes that >>> /usr/local is not protected >>> >>> And brew will …. ( from brew service help ) >>> If sudo is passed, operate on /Library/LaunchDaemons (started at boot). >>> Otherwise, operate on ~/Library/LaunchAgents (started at login). >>> >>> >>> >>> >>> Cheers >>> >>> Enrico >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> <mailto:Oorexx-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> >> > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
