Try it yourself to kill our process in the Task manager - it does not matter and anyway your child will be under controlling of our filtering service.
Idea status:
completed
Comments
Tim C, 14.10.2010, 20:31
It looks like you can kill fltw (something like that) and the current session of the browser can browse freely, but any new sessions (probably any new applications too) are correctly blocked. I assume that is a bug; the daemon restarts on its own after it is killed, it just doesn't have any impact on currently-running sessions then.
TrafficWasher
All the ideas and discussions