Hi Geoff This is becoming a bit of a saga :) below On Wed, 28 Nov 2001 19:55:08 +0000, Geoff wrote:
I am not sure exactly where you are checking the properties, but if you "ls -l ip-up.local" you should see a string of letters and dashes on the left side of the output. The fourth one in from the left will change from a dash to an x when you make the file executable.
Ok it is an exex
If you want to make the file into a pukka shell script the full format is :
#!/bin/bash # Insert here the comment of your choice to remind you what the file is for. # /full/path/to/firestarter > /home/<username>/dampsquib 2>&1 &
If you want a simple test to check whether the file ever executes, you could put the following line before the line that runs firestarter :
touch /home/username/testiplocal
Done that - now getting dampsquib created. The file contains the following Gtk-WARNING **: cannot open display. Can't find testiplocal. So although that command works on the command line, something is not right in the file ??
That will just create a new empty file, testiplocal, of 0 length in your home directory, which (as root), you can then delete. Its creation will prove that ip-up.local executed, and the contents of /home/<username>/dampsquib will show any messages generated by firestarter.
If all this eventually works, then we may need to think about creating an ip -down.local which will terminate firestarter until it is next needed, ... but it feels like tempting fate to go into that now. I love your optimism :)
Incidentally, where, how or what calls Netscape up. Can't find where it is called from.
I do not make much use of Netscape. I believe, however, that when you invoke Netscape the call is to /usr/X11R6/bin/netscape. That is a symlink to the shell script /usr/X11R6/bin/communicator, which contains a variety of tests and commands. To tell the truth, I have never bothered to get to the bottom of that script. That might be an interesting diversion for a rainy afternoon (then again it might not). I might be wrong about all this though.
No, I pointed you to the wrong end. Where is it being called from, I thought maybe wvdial.conf. I tried it there but no go. But maybe I should concentrate on ip-up.local since we now know it is being read. Thanks Regards, David