Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Sep 2003 09:15:42 -0700
From:      rtjohan@syspres.com
To:        freebsd-questions@FreeBSD.ORG
Subject:   when running portupgrade triggering reboot / how to do detailedsystem log to see precise reboot trigger?
Message-ID:  <3F74662E.8060805@syspres.com>
In-Reply-To: <3F698F28.7080902@snu.ac.kr>
References:  <001701c37dd2$9467f170$04fea8c0@moe> <3F698F28.7080902@snu.ac.kr>

next in thread | previous in thread | raw e-mail | index | archive | help
Have not been able to keep machine up-to-date with cvsup since each time 
after the cvsup has completed, the portupgrade reboots the machine.

Probably the first thing to do is to enable some log utility to capture 
what triggered the reboot.
How should I go about this - logging in as much detail to figure what 
happened?

Running FreeBSD 5.1 Release with KDE.

The applications/libraries are all up-to-date except for the list below. 
Seems obvious that upgrading one of those packages triggered the reboot. 
Here are the pieces that are out-of-date from cvsup:
    - arts
    - cdparanoia
    - cups-base
    - esound
    - gconf2
    - gnome-icon-theme
    - gnomevfs2
    - kdemultimedia
    - libbonobo
    - libbonoboui
    - libgnome
    - libgnomeui
    - linux_base
    - p5-Net
    - pcre
    - pilot-link
    - scrollkeeper





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F74662E.8060805>