home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x
- Path: sparky!uunet!cs.utexas.edu!tamsun.tamu.edu!inetg1!cgp
- From: cgp@Arco.COM (Chris Phillips (214) 754-6419)
- Subject: Re: faking xlock with kill -STOP <X server PID>
- Message-ID: <1992Jul23.150228.25846@Arco.COM>
- Organization: ARCO Oil and Gas Company
- References: <1992Jul21.143641.20596@Arco.COM> <1992Jul22.203318.24969@porthos.cc.bellcore.com>
- Distribution: usa
- Date: Thu, 23 Jul 1992 15:02:28 GMT
- Lines: 17
-
- In article <1992Jul22.203318.24969@porthos.cc.bellcore.com> bucci1@donner.uucp (25853-pastor) writes:
- >In article <1992Jul21.143641.20596@Arco.COM>, cgp@Arco.COM (Chris Phillips (214) 754-6419) writes:
- >> $ sleep 5; kill -STOP <X server PID>
- >
- >We were wondering exactly what you meant by "X server PID". When we
- >used the PID for the window manager, the applications still ran, but all
- >input was locked out. If we stopped the original ksh, the window manager
- >still allowed the user to close the window of the original xterm (and thus
- >terminate that display completely).
-
- $ ps -e # your flags may vary
- [...]
- 14517 hft/0 0:17 X
- [...]
- $ sleep 5; kill -STOP 14517
-
- Chris
-