-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

When I get the error message that firefox is already running, I simply
killall firefox-bin.  I have not seen firefox hose NFS before (though to
be fair, NFS could be hosed and I wouldn't know it, since I do all my
file serving over CIFS, NFS is there merely as a toy).

For robust remote access I still use old school serial (rs232) console
access. You can even interact with Grub over serial.

You will need a null modem serial cable, and two machines close enough
to connect via serial.

In your /boot/grub/menu.lst file add the following:

# Setup serial (COM1) here with baudrate 38400
# use --unit=1 (for COM2) and so on
serial --unit=0 --speed=38400
#
# Now setup terminal as both Serial Line(/dev/ttyS0) and
# Monitor Console(/dev/tty0) depending upon where you press key
# with in timeout (15 sec) period. Otherwise first entry
# (console(Monitor)=>tty0) is selected here.
terminal --timeout=15  serial console

You of course don't need the comments but they are useful to remind you
what is going on.

You then need to add the following line to your /etc/inittab:
T0:23:respawn:/sbin/getty -L ttyS0 38400 vt102

- From the client machine you need some sort of program to communicate
over serial, I have used minicom and gtkterm.  I prefer minicom, and
likely this is what you will use remotely inside of an ssh session (ie.
you ssh to the "client", which then connects to the server via serial).

I have used a USB to serial dongle on the client side, but have never
tried it on the "server".

Cheers,


Tom Weniger wrote:
> Greetings All,
> 
> I would like to share this little annoyance I have with Firefox. My
> home network connects 2 PCs and a laptop. They share files via NFS and
> I have a 7 year old daughter that likes to blow up the network by
> running more than one session of Firefox.
> I found that if I tried to run Firefox in the client PC this morning,
> a requester would pop up and announce that it is already running and
> that I should end the session or reboot the PC. I checked the .mozilla
> folder and found a lock file with a broken link which I deleted. Next,
> I ran 'ps -A| more' and found that lockd was running. Next, I checked
> the gconf-'daughter' folder in tmp and removed the lock folder. I had
> seen this occur before whenever the NFS service hung up on my network.
> So, I went to the server and shut down the lockd service and reinit
> the server. Everything came back up and Firefox works properly on the
> client PC.
> I was wondering if it is possible to reinit remotely via ssh. I don't
> think so since the ssh session would be lost and presumably I would
> hose the network with a broken link and/or a lock file. Has anyone
> tried this procedure? Or is there a better mousetrap available?
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFNQYUwRXgH3rKGfMRAulwAJsGwqQwDtmfVTwGWs9lsic75ULwswCgg+ar
OEGMNqmhbwEVRcPirTJcZVE=
=N/Zq
-----END PGP SIGNATURE-----

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to