Michael W. Lucas wrote:
On Wed, Feb 08, 2006 at 10:58:45AM +0100, Gerard Milhaud wrote:
Michael W. Lucas wrote:
Hook up a serial console, and use script(1) to capture any panic
messages, etc. That'll give you a hint as to what's going on, and you
can see how to proceed.
Thanks a lot for your answer... But how can I use script, because when
the problem happens, all the processes are frozen and the file script is
being writing is not saved...
And which process/command do you suggest I attempt to audit ???
Use script on the machine acting as your console. If it's a Windows
box, hyperterm has a "capture to file" option that will work as well.
OK. I've disbaled soft-updates on /. I've sysloged *.info (and therefore
*.x where x is more critical than info) to /var/log/all.log.
When the X freeze comes, I've no accurate message in my log file...
Do you think an external console machine could give me more info ??
It's very hard to figure this out within x11.
(Yes, this is a pain, but it could be worse; I'm currently doing a
binary search to figure out when, exactly, -current stopped booting on
my laptop. :-)
Argh !!! I'm not alone lost at the edge of the road...
Good luck...
No, there are quite a few of us here. Welcome to the cutting edge. :-)
Maybe too much sharp-edged for me...
Bye and thank you for any idea...
--
Gérard MILHAUD
École Supérieure d'Ingénieurs de Luminy (ESIL)
Université de la Méditerranée
Coordonnées : http://annuaire.univ-mrs.fr/showuser.php?uid=milhaud
--
[Détente] Essayez donc mon tireur au sort de citations marseillaises :
http://planete-marseille.esil.univ-mrs.fr/les.cgi-bin.a.G/citations.pl
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
