If it's what I think you mean (Ctrl-S stopping output on your terminal screen) then I don't think it's really an interrupt - it's an RS232 thing, Ctrl-S stops everything and Ctrl-Q starts it all again.
Why do you need to stop it? If it's because you're users are pressing Ctrl-S inadvertently would it be possible to re-map that keystroke combination in their terminal emulation s/w? (Assuming they're using PC's and not terminals of course)
Mike
michael.j.lacey@ntlworld.com
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.