From: SourceForge.net <no...@so...> - 2010-01-18 15:48:24
|
Bugs item #2933987, was opened at 2010-01-17 14:14 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2933987&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jeremy C B Nicoll (jeremynicoll) Assigned to: Nobody/Anonymous (nobody) Summary: two rxapi.exe tasks, Initial Comment: ooRexx 4.0.0, Windows XP Pro SP3 - sorry I have no idea what "category" value this report should be under A few days ago I looked at task manager in Windows, and noticed two entries for rxapi.exe. Normally there'd just be one; rxapi.exe does start as a service. I don't know what caused this. I'd assumed that rxapi would have defined/tested a semaphore/mutex or whatever and even if a second example started, one would die and let the first one carry on. ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2010-01-18 07:48 Message: The rxapi executable can be started from the command line. If rxapi is already running as a service, this can produce two rxapi rpocesses. C:\work>pslist rxapi pslist v1.28 - Sysinternals PsList Copyright ⌐ 2000-2004 Mark Russinovich Sysinternals Process information for SDC91593C1: Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time rxapi 4552 8 2 38 464 0:00:00.046 0:18:34.678 C:\work>rxapi C:\work>pslist rxapi pslist v1.28 - Sysinternals PsList Copyright ⌐ 2000-2004 Mark Russinovich Sysinternals Process information for SDC91593C1: Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time rxapi 4552 8 2 38 464 0:00:00.046 0:18:42.444 rxapi 3012 8 1 30 500 0:00:00.062 0:00:04.656 C:\work> Only one process can run as a service: C:\work>sc stop rxapi SERVICE_NAME: rxapi TYPE : 10 WIN32_OWN_PROCESS STATE : 3 STOP_PENDING (STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 C:\work>pslist rxapi pslist v1.28 - Sysinternals PsList Copyright ⌐ 2000-2004 Mark Russinovich Sysinternals Process information for SDC91593C1: Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time rxapi 3012 8 1 30 500 0:00:00.062 0:03:29.341 C:\work>sc stop rxapi [SC] ControlService FAILED 1062: The service has not been started. C:\work> You can end the second process using taskmanager or some other process manager: C:\work> C:\work> C:\work>pslist rxapi pslist v1.28 - Sysinternals PsList Copyright ⌐ 2000-2004 Mark Russinovich Sysinternals Process information for SDC91593C1: Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time rxapi 3012 8 1 30 500 0:00:00.062 0:05:42.342 C:\work>pskill rxapi PsKill v1.12 - Terminates processes on local or remote systems Copyright (C) 1999-2005 Mark Russinovich Sysinternals - www.sysinternals.com Process rxapi killed. C:\work>pslist rxapi pslist v1.28 - Sysinternals PsList Copyright ⌐ 2000-2004 Mark Russinovich Sysinternals Process information for SDC91593C1: process rxapi was not found on SDC91593C1 C:\work> rxapi uses sockets to do its work. The first process that starts is going to grab the communication port, so there is no way that I can think of that the second process can hinder the function of rxapi, or does any real harm. So, preventing a second process from starting would not be real high on my list of priorities. Of course, if you can come up with a scenario that starts a second rxapi process, that doesn't involve manually staring it from the command line, I'd be intersted in that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2933987&group_id=119701 |