Article View: comp.windows.x
Article #23933xlock problem solved (stupid me)
From: Zube
Date: Fri, 21 Jun 1991 05:14
Date: Fri, 21 Jun 1991 05:14
13 lines
807 bytes
807 bytes
I missed it. It was in the man pages, and even though I thought I had read them thoroughly, I blew it. The answer was: use xlock -remote. I apologize for the question. I also thank those who replied so promptly and especially thank those who didn't flame me or say "RTFM. Are you stupid?" Thanks, John dzubera@mozart.cs.colostate.edu dzubera@lamar.colostate.edu
Technical Details
Message-ID:
<15612@ccncsu.ColoState.EDU>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!ccncsu!mozart!dzuberaShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!ccncsu!mozart!dzubera From: dzubera@mozart.cs.colostate.edu (Zube) Newsgroups: comp.windows.x Subject: xlock problem solved (stupid me) Message-ID: <15612@ccncsu.ColoState.EDU> Date: 21 Jun 91 05:14:33 GMT Sender: news@ccncsu.ColoState.EDU Organization: Colorado State University Lines: 13