At 03:14 a.m. 23/12/2005, you wrote: >freenetwork at ... <freenetwork at ...> writes: >-- snip -- >> The freenet node runs with the name "javaw.exe". But if you don't know the >> exact PID, simply killing by name >> might affect other java programs running as they all have the same process name (java or javaw). >> "freenet.exe" is just the bunnyapp > >Yeah, but the process tree is freenet.exe -> Flaunch.exe -> javaw. Sysinternals >pskill, at least, has the ability to kill a process and all its "descendants" >(with the -t switch), so provided they are considered descendant processes you >should be able to kill freenet.exe and take the rest of freenet (only) with it.
Sorry perhaps I should have been more clear. If you kill (send close signal)freenet.exe, you kill the icon only. I said the frontend but I don't know whether it is the complete frontend because freenet.exe is still a running process. You can try to kill it again and it says sending signal but it doesn't close. If you try it too much, it says unable to close, need to force. The only way to kill freenet.exe completely is to force. However a further check reveals you're right, javaw.exe does not die even if you force kill the freenet.exe. The javaw.exe process also does not respond to a request to end so you also have to force kill it. Of course, the point about javaw.exe potentially being more then one process is a valid one but process ID is completely unsuitable. The whole point is to allow a simple command line kill so it can be set for a scheduler. There is no point if you need to update the process ID all the time. Systernals I suppose might work but it still doesn't solve the problem that freenet does not die gracefully when requested. Also, it means that you may kill an open browser window which you opened with the frontend which I guess is a dependent which you may not want to kill. I still think it's best to have a command line end task with the front end or at least when you ask the frontend to close, it should close properly and close both the frontend and the backend but obviously not browser windows. If you really want to just close the front end. I guess an option in the front end to close the front end may be useful. Maybe consider for 0.7
