It might not be true for the Mac, but I believe it is true for Linux, which means just changing that line is not the correct behavior.
I just discovered that the source tree has a Mac version of APIServer.cpp that uses a tmp file, but the build is unconditionally using the Linux version. Not sure when or who created that file, nor why it is not being used. Rick On Wed, Nov 21, 2018 at 11:04 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > > > On 21 Nov 2018, at 15:23, Rick McGuire <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 > 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
