>
> *Re: [Oorexx-devel] More Building 4.0 on OpenBSD 4.3*
> From: Rick McGuire <[EMAIL PROTECTED]> - 2008-10-11 17:23
> ooRexx has launches a daemon process call rxapi, which is used to
> manage the IPC used for queues, function registrations, and
> macrospace. That process is started when required, and converts
> itself to a system daemon that continues to run when the spawning Rexx
> process terminates.
>
Building with latest svn revision 3577:
* Builds without patches.
* rexx can't start rxapi since it wants to write a pid to /var/run
o rxapi has to be started sudo
* if rxapi is not started, rexx ends up forking a rexx process and
both hang
o the second is left spinning at hi CPU usage when ^C out of
the foreground
* if rxapi is not started, rexx still hangs while trying to make
rxapi call
o but on ^C out the process goes away cleanly
So apparently what I've been ^C'ing out of is the fork that's trying to
start rxapi. Then
I'm left with the caller spinning. Starting rxapi via sudo avoids that,
and all I have is
the caller spinning which can be killed in the foreground.
None of this changes what you said, Rick, but it seemed interesting at
05:30 sunday morn :)
--
Jack J. Woehr # "Self-delusion is
http://www.well.com/~jax # half the battle!"
http://www.softwoehr.com # - Zippy the Pinhead
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
