Viewing SSH Connection
kyle at xraided.net
Tue Jun 8 07:03:58 GMT 2004
It was a kernel panic, but of course I didn't have enough space on /var:
Jun 7 23:41:59 smith savecore: reboot after panic: page fault
Jun 7 23:41:59 smith savecore: no dump, not enough free space on device
(261612 available, need 395776)
So, I'm SOL this time, but I'm freeing up space as I type, in case this
happens again (and checking my other systems to make sure they have
enough free space in /var too!) :D
As long as I do the 'kldunload snp.ko', I should be ok, right? Don't
need to worry about /dev/snp* ?
> -----Original Message-----
> From: owner-freebsd-stable at freebsd.org [mailto:owner-freebsd-
> stable at freebsd.org] On Behalf Of Dariusz Kulinski
> Sent: Monday, June 07, 2004 11:59 PM
> To: Kyle Mott
> Cc: freebsd-stable at freebsd.org
> Subject: Re: Viewing SSH Connection
> Hello Kyle,
> Monday, June 7, 2004, 11:41:46 PM, you wrote:
> > Several people have suggested using the snp.ko and watch, which
> > great.
> > However, I didn't want to have the devices just sitting around so
> > someone else on the system could use it, so I did 'kldunload snp.ko'
> > then rm -f /dev/snp0... My system seems to be freaking out. Did I
> > something? Actually, I think I just had a kernel panic. *sigh*
> I think you shouldn't be afraid to having /dev/snp0 device, anyway
> only root can use watch command.
> But if your system has crashed there probably is a bug in freebsd. I
> know I had a crash with watch, but at that time I had loaded 3rd party
> module so I blamed that crash on it. Also I didn't have kernel
> compiled in debug mode. If you had a crash that would suggest that
> there actually is a bug in snp.ko module.
> Maybe there is somebody from devel team who could comment on that
> Best regards,
> Dariusz mailto:takeda at takeda.tk
> CCNA, SCSA, SCNA, LPIC, MCP certified
> freebsd-stable at freebsd.org mailing list
> To unsubscribe, send any mail to
"freebsd-stable-unsubscribe at freebsd.org"
More information about the freebsd-stable