If you remember I struggled with rxapi, because the Mac documentation says that a process started by Launch Services should not daemonize itself, which rxapi does. I did get it to run, but I think I just found what they were talking about.
09/27/10 9:01:45 AM org.rexxla.oorexx.rxapid[5197] Error: There is already a server running. 09/27/10 9:01:45 AM org.rexxla.oorexx.rxapid[5197] Aborting execution. 09/27/10 9:01:45 AM com.apple.launchd[1] (org.rexxla.oorexx.rxapid[5197]) Exited with exit code: 255 09/27/10 9:01:45 AM com.apple.launchd[1] (org.rexxla.oorexx.rxapid) Throttling respawn: Will start in 10 seconds So because rxapi does basically a fork and exec to daemonize itself. Then the parent process exits, with an exit code of 0. Since the parameters I've given Launch Services is to always keep rxapi running, Launch services relaunches the daemon, which then detects the running daemon, and exits with a return code of 255. This cycle of launching the daemon continues every 10 seconds. I could change the parameter from launch at load to launch on demand, which would cause the daemon to launch anytime a bind is processed against the well known rxapi port. I don't know if that would help because as long as the port is bound it would keep relaunching the daemon. Any thoughts on how rxapi can be changed into a pure daemon. Thanks, Bruce ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
