[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Running 'xosview' with XDM
- From: Cameron Simpson <cs zip com au>
- To: Steve Frampton <frampton alcdsb on ca>
- Cc: redhat-list redhat com
- Subject: Re: Running 'xosview' with XDM
- Date: Mon, 1 Feb 1999 02:49:02 +0000
On 1 Feb 1999, in message <Pine LNX 4 05 9901312115090 7660-100000 mail flarc edu on ca>
Steve Frampton <frampton alcdsb on ca> wrote:
| > Indeed. But _don't_ use killall - you can easily inadvertantly nail
| > things you didn't want nailed (especially running as root, but even as
| > an ordinary user if you have multiple sessions). Stuff the pid into a
| > file and kill just that pid later:
| > [xosview ... &]
| > echo $! >/var/run/xosvPid.$DISPLAY
| > and in GiveConsole
| > kill `cat /var/run/xosvPid.$DISPLAY`
| > rm /var/run/xosvPid.$DISPLAY
| > which scales to multiple DISPLAYs and kills very accurately.
| Exactly...that was a concern of mine. Hmmm...my xosview that I just
| loaded up 2 minutes ago was just killed 'cause somebody else logged in?
| ;-)
| Thanks for this great hack. I had thought about something similar but
| your multiple display idea rocks...
If you're going to use it, make sure you use quotes:
echo $! >"/var/run/xosvPid.$DISPLAY"
In normal circumstances (indeed, _all_ that I can think of) there
shouldn't be any weird chars in the DISPLAY variable, but this tiny
quoting fetish makes you safe from the more egragrious things.
Oh, and you probably want to remove /var/run/xosvPid.* at boot...
--
Cameron Simpson, DoD#743 cs zip com au http://www.zip.com.au/~cs/
My initial work-around is to rebuild history.
- gary sci34hub sci com (Gary Heston)
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]