Hi Geoff On Thu, 6 Dec 2001 09:09:38 +0000, Geoff wrote:
OK .. time for a little theory. Your X server identifes its displays by two numbers, starting with 0:0. When you start a server you get ownership of a display, starting with the 0:0 default. This becomes part of your "environment". If you enter
whilst running an X session you will see the value of that default display. There is a security check which stops other people from accessing your display without permission. Thus if you are running an X session as <username> and you su to root and try to run something that uses X then you will see access denied - or some equivalent message. You can give others permission to access your display in various ways. The quick and dirty way is
which simply kills the security and lets anyone in. There are better and more secure ways which do not involve you in typing every time, but there is no point in setting those up until we know that it helps. The ip-up.local script runs as root. When first you tried it dampsquib reported the Gtk error that the display could not be opened. I thought that this was a problem that could be cured by
, but that turned out not to be the case, and if you were running X as root I suppose that should not be surprising, because I think that in those circumstances root would own display 0:0. When I installed F/s I was running as my own <username> and I had used
to allow root access to the display. Even so, I saw the self-same Gtk "could not open display" error in my dampsquib. A little research showed that this is a known problem and that root needs to have a display set as part of his environment to cure it. All that my ip-up.local does is to set root's environment to use 0:0. It worked immediately and I ran about 20 tests without fail. Now, if you are running everything as root, I would not expect the export line in my ip-up.local to make such a difference - because root already owns the display. I therefore went back and did some experiments this morning, using my old unloved kde setup as root. Here is what I found :
That's interesting - didn't know any of that
(1) Root must still execute
before the first attempt to contact the ISP. (2) This cures the cannot access display problem *but* there is another problem, which, because of an accident in the sequence of events when I ran my tests last Saturday, did not then arise. It seems to be linked to an aspect of gnome (not exactly sure which yet), that ip-up.local has problems starting. Before I work out a fix, will you please test that your system behaves the same way as mine, so far, by carrying out the following protocol :
(a) Reboot
(b) Enter
and confirm that the response is : "access control disabled, clients can connect from any host"
Yes, the same
(c) Logon to your isp and start F/s by hand from the command line. The aim here is to initialise the bits of gnome that it needs and which can apparently be started from the command line but which ip-up.local does not yet initialise. This seems to be a once and for all process which will last until you next restart X.
(d) Close F/s and logoff from your isp.
Yes
(e) Logon to your isp again.
Yes
In my system that will have the result that F/s starts automatically from ip -up.local. If it is the same for you, then we just have to work on a fix for the gnome thing.
Now we differ. Yes F/s starts up automatically, but the system appears to freeze, it hasn't but it is extremely slow, to the extent that it takes about 30 secs to bring any window to the front. On the kinternet log it gets as far as pppd secondary address DNS xxx.xxx.xx.xxx and stays like that, then I get pppd terminating due to lack of activity and it disconnects. The system is then back up to speed, except for F/s that takes forever to repaint its window, 30 secs +. It seems that F/s is slowing the system loading it this way. Rebooting and doing it manually, if I load F/s just after ip-up has run, then it will prevent the browser connecting. If I stop it and get the browser going, start F/s (this is just using the stop start buttons) then it is fine. Have you set yours for masquerading? As an alternative solution, I have found where in Yast2 Netscape is loading. I want to put Netscape & firestarter to load one after the other. Can you load 2 programs on one line? I tried netscape; firestarter. This loads netscape, and when it is shut down loads firestarter, not quite what I want. Regards, David