Re: [Wrapper-user] Can't make old wrapper daemon go away

[Mark L. <mid...@ve...>]

Mark Leone wrote:
> I made some changes to my wrapper application on Mac OSX, and I can't 
> make the old version go away. Perhaps this happened because I checked 
> "Open at login" in the dock. I run the new version of the app and it 
> can't run because the old version is running and has the IP port locked 
> up. So I find a java process with parent process = wrapper, and I kill 
> it, and it comes right back. I've looked in all the LaunchDaemons 
> folders and StartupItems folders, and I can't find what's making this 
> old version of the app start up over and over. When I execute "myAppName 
> status" I see that it's not running. But the old version is still 
> running, and I don't know how to kill it permanently.
>
> -Mark
>
>   
This seems to be another manifestation of the problem I reported in an 
earlier thread, which was fixed by the new script found at

http://wrapper.svn.sourceforge.net/viewvc/*checkout*/wrapper/trunk/wrapper/src/bin/sh.script.in.

But I just re-loaded that script again to make sure I didn't somehow 
revert to the old one, and I still have the same problem. I'm having 
this problem with two separate applications that I'm running via wrapper 
on OSX. My executables renamed from script.sh.in are RCBServer and 
RCBClient. For example, I type "./RCBServer start" and I get what looks 
like a normal startup. Then I type "./RCBServer status" and I get

Removed stale pid file: /Applications/Remote 
Clipboard/RCBServer/bin/./RCBServer.pid
RCBServer is not running.
Mac-mini:/Applications/Remote Clipboard/RCBServer/bin Martha$

And I can't stop the daemon now because wrapper thinks it's not running. 
The only way I can stop it is to kill the process named wrapper.