On Thu, Dec 27, 2018 at 2:22 PM Erich Steinböck <erich.steinbo...@gmail.com> wrote:
> go ahead and make the changes and commit > > Committed revision 11649 (for Unix-like systems only) > This now uses the username in the service/lock file path. > Uses XDG_RUNTIME_DIR or /tmp, but never ~ > rxapi now prints to the stdout > > There's one thing about rxapi: I don't see what we try to achieve with the > `sigaction(SIGTERM, &sa, NULL)` section. > I don't see any way rxapi could end gracefully. If stopped by whatever > signal it just ends immediately. > I just kept what was there originally. Perhaps there was some requirement for this to run as a system daemon, which makes that a bit obsolete. If there is a better way to handle this, go for it. Rick > > > On Thu, Dec 27, 2018 at 11:48 AM Rick McGuire <object.r...@gmail.com> > wrote: > >> Since it runs in a different process in normal operation, we could >> probably just unconditionally put out some messages indicating the source >> of the problem. Then if someone appears to be having issues, we can just >> ask them to start it from the command line and report the errors. >> >> But yes, go ahead and make the changes and commit. >> >> Rick >> >> On Thu, Dec 27, 2018 at 4:16 AM Erich Steinböck < >> erich.steinbo...@gmail.com> wrote: >> >>> Have you done anything else with these changes? >>>> >>> >>> Not yet. I can do the change to use getpwuid() and commit, if you agree. >>> >>> What do you think regarding finding out whether rxapi runs or why it >>> couldn't start? Maybe add an option to the rxapi command? >>> This would help (us) with support requests like "Rexx queuing doesn't >>> work for me -- why?" >>> >> _______________________________________________ > 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
