home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x
- Path: sparky!uunet!centerline!noc.near.net!news.Brown.EDU!qt.cs.utexas.edu!cs.utexas.edu!tamsun.tamu.edu!inetg1!cgp
- From: cgp@Arco.COM (Chris Phillips (214) 754-6419)
- Subject: faking xlock with kill -STOP <X server PID>
- Message-ID: <1992Jul21.143641.20596@Arco.COM>
- Organization: ARCO Oil and Gas Company
- Distribution: usa
- Date: Tue, 21 Jul 1992 14:36:41 GMT
- Lines: 14
-
- Unfortunately xlock doesn't just sleep; it does hinder the
- execution of other processes. But if the X server is
- SIGSTOPped, won't this have the same effect? The only drawback
- I see is that you will need to login somewhere else and send it
- a SIGCONT.
-
- Of course, keystrokes are not ignored and you should do something
- like
- $ sleep 5; kill -STOP <X server PID>
-
- Then move the pointer to the root window.
- Are there any security problems with this?
-
- Chris
-