Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!point.cis.ohio-state.edu!keith From: keith@point.cis.ohio-state.edu (Keith M Boyer) Newsgroups: comp.sys.hp Subject: Re: Disabling Message-ID: <92629@tut.cis.ohio-state.edu> Date: 8 Mar 91 22:31:31 GMT References: <91491@tut.cis.ohio-state.edu> <7370335@hpfcso.FC.HP.COM> Sender: news@tut.cis.ohio-state.edu Reply-To: Keith M Boyer Organization: The Ohio State University Dept of Computer & Information Science Lines: 27 In article <7370335@hpfcso.FC.HP.COM> stroyan@hpfcso.FC.HP.COM (Mike Stroyan) writes: |> We have been running the X11R4 server code from MIT and are mostly happy. |> One small problem is that there does not appear to be an easy way to |> disable . This makes xlock rather useless. Has anyone |> got a way to disable this feature. Thanks. | |There is an HP extension to control this which is documented in |"Programming With Xlib", Appendix E, section E.4, "Locking an X Display". |Disable the sequence with XHPDisableReset(display). Enable it with |XHPEnableReset(display). When we were using HP supplied X11R3 these were available and we did, in fact, use them. Perhaps I was not as clear as I should have been. The MIT X11R4 Server does not have the XHP* extensions in it. Using the X11R4 Xlib does not provide any obvious way of keeping this key sequence from terminating the X server. Is there another way to deactivate this? ++keith -=- - Keith M. Boyer Department of Computer and Information Science -- THE Ohio State University 2036 Neil Ave. Columbus OH USA 43210-1277 - keith@cis.ohio-state.edu or ...!osu-cis!cis.ohio-state.edu!keith NO CENSORSHIP, NO SOFTWARE PATENTS --- SUPPORT THE FREE FLOW OF INFORMATION