WM_KILL on connection running script

[Mouton]

What happens when u try to WM_KILL a connection that currently is running a script ?

I'm trying to see why when i try to kill all connections that are inside a specific dir on nuke, it sometimes says that it' can't kick all users from inside the dir (so ioA can't rename it)...

[Mouton]

well, i tried to do a big rescan, and on nuke, the connection can't be WM_KILLed... it does nothing.

a site kick would kick the user once the script has finished running, but a kill won't do that.

I don't see how one could nuke correctly...

any thought ?

[Mouton]

I think my best bet would be to loop that WM_KILL and sleep for like 1/4s between each try... for like 3s... or until all users are killed... should work.

[Mouton]

i did some more tests......
now, WM_KILL returns 0 even if user is running a script, and his connection is forced closed when script is done... :|

[10:29:50] Error: 10054:Connection reset by peer
[10:29:50] Connection lost: 127.0.0.1

[darkone]

Yes, connection is closed after script finishes.. terminating script, wouldn't be very nice option :p