[lug] Daily system crash....

Michael Hirsch mdhirsch at gmail.com
Tue Feb 5 21:21:31 MST 2008


On Jan 28, 2008 11:59 AM, David Morris <lists at morris-clan.net> wrote:
> On Sat, Jan 26, 2008 at 10:19:39AM -0700, Ted Logan wrote:
> > On Jan 25, 2008 12:12 PM, David Morris <lists at morris-clan.net> wrote:
> > > I have a strange problem with my system I'm hoping for input
> > > on.
> >
> > If you have a null modem cable handy, and another Linux box nearby,
> > you can set up Linux to output kernel log messages (hopefully
> > including messages indicating the fatal error) over the serial port.
> > This HOWTO will tell you what you need to know:

No need for a null modem cable.  Just have syslog log to another
machine on your network.  That can even go over the wan, though I'd
just to it to another machine, assuming you have one handy.

> Worth a try, though I don't have such a cable on-hand.
>
> A few updates on the problem:
>
> I did realize another variable which changed about the time
> I first noticed the problem:  I started connecting to a VPN
> using the Cisco VPN client.  I have no clue if the problem
> started before or after I first connected the VPN, but it
> was near the same time.  Of course, it was also about the
> same time that I started using the system as a development
> platform on a regular basis, so again it could just be
> coincidence.

I didn't realize that cisco support 64 bit in linux, yet.  I don't use
it, I use vpnc.  It was really easy to configure and works great.  I
can eaven use my RSA SecurID card with our cisco vpn.  vpnc has no
kernel part, too, which is nice.

Michael



More information about the LUG mailing list