after the reboot the device will have been completely reset and thus the command is pretty much pointless in analysing the fault.. why did the machine crash? there are certain debugging tools you can run if you know what command caused the issue.. or application, tools include gdb and strace, and when submitting bug reports to developers are always helpful to include


On 04/04/06, stuart bell <sailing1@gmail.com> wrote:
Andrew,
 This is after a restart cos it froze up on me!
Stuart
Password:
[root@localhost ~]# ifconfig -a

eth0      Link encap:Ethernet  HWaddr 00:60:4C:62:B9:3E
          inet6 addr: fe80::260:4cff:fe62:b93e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:65535  Metric:1
          RX packets:187 errors:0 dropped:0 overruns:0 frame:0
          TX packets:215 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:85541 (83.5 KiB)  TX bytes:39874 (38.9 KiB)


lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask: 255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)


ppp0      Link encap:Point-to-Point Protocol
          inet addr:84.13.33.133  P-t-P: 84.13.0.1  Mask:255.255.255.255

          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:165 errors:0 dropped:0 overruns:0 frame:0
          TX packets:190 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:84908 (82.9 KiB)  TX bytes:35230 (34.4 KiB)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@localhost ~]#                   

On 04/04/06, Andrew Edwards < edwards.andrew@gmail.com> wrote:
appears to make sense, when this happens referring to the old error with RX packets just check your "ifconfig -a" to see if there are a certain number more errors there than before, if a pattern occurs it's more likely to be a software bug, if there is no pattern then i'd assume it's a manufacturer hardware defect, and no.. questions are why we have the lists


_______________________________________________
Staffslug mailing list
Staffslug@staffslug.org.uk
http://www.staffslug.org.uk/mailman/listinfo/staffslug





--
Andrew J. Edwards
www.andrewedwards.name
Tel: 07900581454