>>> Right now this isn't directly possible via freenet.exe (the systray app) as >>> far >>> as I can tell. It does take command line args, but not a shutdown one. It >>> could >>Heh ignore that, I'm an idiot, obviously running freenet.exe -shutdown to call >>ExitFServe would spawn a new process then shut it down rather than affecting >>an >>existing one :) It would have to look for another instance of itself, post >>stop/exit messages to it and then quit. This is unneccessarily complex though, >>process killing should work one way or another. > >Good news I found a way that kind of works and doesn't require any external >programs. taskkill.exe comes with Windows and can be used to end >tasks/processes from the commandline. Unfortunately, Freenet doesn't work >properly with taskkill. In theory, 'taskkill /IM freenet.exe' should end Freenet but it only ends the front end. Freenet remains in the background. Repeating the function does not help (it says send the signal but the process does not end). I guess Freenet backend does not respond to Windows end task signal for some reason. An alternative, you can use 'taskkill /IM freenet.exe /F' which forces Freenet to end but of course this means it's not a clean shutdown. While I still think a command line shut down switch would be useful, at the very least Freenet should respond properly to a Windows end task signal. > >Thanks Matthew for your help to approve my message as I used a remailed for >anonymity purposes.
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 (Yes, this confusion arises quite often but nobody cares to give this, IMHO totally superfluous (hopefully 0.7 comes without all these stupid extra-programs), app a proper name).
