> > > Tried the reboot. Same results. > > Tried several other CL starts. It seems to now run for only about three > minutes. Here's the results from tail /var/log/message > > linux:/home/regis # tail /var/log/messages > Oct 9 16:36:38 linux gconfd (root-6474): Exiting > Oct 9 16:47:11 linux su: (to root) regis on /dev/pts/1 > Oct 9 17:10:28 linux syslog-ng[4264]: STATS: dropped 0 > Oct 9 17:38:49 linux udevd[2302]: get_netlink_msg: no ACTION in payload > found, skip event 'mount' > Oct 9 17:38:49 linux udevd[2302]: get_netlink_msg: no ACTION in payload > found, skip event 'mount' > Oct 9 17:38:52 linux udevd[2302]: get_netlink_msg: no ACTION in payload > found, skip event 'umount' > Oct 9 17:38:52 linux udevd[2302]: get_netlink_msg: no ACTION in payload > found, skip event 'umount' > Oct 9 18:10:28 linux syslog-ng[4264]: STATS: dropped 0 > Oct 9 19:10:29 linux syslog-ng[4264]: STATS: dropped 0 > Oct 9 19:51:48 linux su: (to root) regis on /dev/pts/1 > linux:/home/regis # > > It seemed like the crash came a few minutes after the time stamp on the > last entry, but I checked the file manually and that is these are the > last entries. > > The download seems to be getting right up to 2 gig, then dieing. Is it > possible that there is some upper limit on the download size? I checked > the configuration and all items show "no limit". Maybe I just need to > send for the boxed edition! > > Any suggestions are appreciated! > > Regis >
Sorry about responding to my own post but the latest "tail" yielded what looks like some more meaningful information: linux:/home/regis # tail /var/log/messages Oct 9 18:10:28 linux syslog-ng[4264]: STATS: dropped 0 Oct 9 19:10:29 linux syslog-ng[4264]: STATS: dropped 0 Oct 9 19:51:48 linux su: (to root) regis on /dev/pts/1 Oct 9 20:10:29 linux syslog-ng[4264]: STATS: dropped 0 Oct 9 20:14:59 linux udevd[2302]: get_netlink_msg: no ACTION in payload found, skip event 'mount' Oct 9 20:15:02 linux udevd[2302]: get_netlink_msg: no ACTION in payload found, skip event 'umount' Oct 9 20:30:07 linux syslog-ng[4264]: SIGHUP received, restarting syslog-ng Oct 9 20:30:09 linux syslog-ng[4264]: new configuration initialized Oct 9 20:30:29 linux kernel: klogd 1.4.1, ---------- state change ---------- Oct 9 20:31:43 linux su: (to root) regis on /dev/pts/1 linux:/home/regis # Don't know where the SIGHUP came from, but I'm guessing that's what shut it down. all thoughts welcome! Thanks, Regis -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
