Linda Walsh wrote:
> Yeah, know about that one:
> (xosview&)
> saves it from the HUP's when the window closes...
No need for that (which adds an unnecessary extra fork), just unset
the bash option huponexit (probably in your ~/.bashrc):
shopt -u huponexit
Although I think that's the defaul
j...@asyn.org wrote:
Have you added the client to your X server's acl? See xhost(1)
---
I thought I'd turned off access checking. I forgot I had to redo
my script when there was a major X-server upgrade, a few months ago --
Not something I 'normally use'...
(Am pretty safe, regardl
Disregard the bit about the client dieing if you close the terminal. The
problem seems to have been fixed (it's been a LONG time since I tried it).
On Sun, 19 Jul 2009, j...@asyn.org wrote:
> Also, running your X client in the background does not disconnect it from
> the terminal from which you
On Sat, 18 Jul 2009, Linda Walsh wrote:
> Yes I've read the FAQ -- it doesn't help. Is says:
>
>
> The problem is most likely a wrong DNS (Network name resolution). Make sure
> your windows host has a hostname which is valid from linux too and an IP
> address which linux can resolve to that hostn
Yes I've read the FAQ -- it doesn't help. Is says:
The problem is most likely a wrong DNS (Network name resolution). Make sure
your windows host has a hostname which is valid from linux too and an IP
address which linux can resolve to that hostname.
---
What DNS resolution?
If you ad