On Thu, 6 Dec 2001 00:58:07 +0000
David wrote:
Hi Geoff
Got Firestarter back up again - ok I can here the groan.
No groans - except of sympathy.
I put your ip-up.local in, and if I run it directly it loads Firestarter, but
not when called from ip-up, though in the kinternet log it shows that ip-up
was
successfull. It is being called in ip-up by
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# call ip-up.local if it exists and is executable:
test -x /etc/ppp/ip-up.local && /etc/ppp/ip-up.local "$@"
;;
ip-down)
# Restore the nameservers (got with ipppd option ms-get-dns):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Is this correct, or does it need altering.
That looks correct to me - it is identical to mine.
"access control disabled, clients can connect from any host"
should come after ...
I think that you will have to enter my command before you go
online.
Remember that you enter that as your own username and you should see
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 :
(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"
(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.
(e) Logon to your isp again.
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.
Regards,
Geoff
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com