On 07/03/2014 09:49, lina wrote: > On Friday 07,March,2014 10:35 PM, Dan Purgert wrote: >> [...] > > Something really weird, my icedove, 6 hours ago popped up an email which > was 2 months ago as unread, couple of mins ago, it also popped up > another email as unread also from that thread, the same person with > yahoo address. >
If it's email (e.g. from some...@yahoo.com to y...@uni.edu), then it could be that your email server lost it, or had it accidentally replicated because they had to restore something unrelated from a backup. Alternatively, it could be the other person's mail client (TB, Outlook, whatever) was finally able to send the message. If you're familiar with reading mail headers, you can dig up the date that the thing was actually transmitted. > I asked my another colleague and was suggested to do the virus check. > right now I am checking which package can be used to scan the virus. > You can try ClamAV. I think it's part of the main Debian repos. >> >> You can check how fast your connection is by running the command >> "ethtool eth0 | grep Speed" (sans quotes). This will tell you the link >> speed between you and the next hop (switch or router). Most networks >> should show 100Mb/s, though you could possibly also see 10 or 1000, >> depending on > > # ethtool eth0 | grep Speed > Speed: 100Mb/s > OK, so your link between you and the next higher up device is 100Mb/sec. What this means is that you have a solid connection between your PC and the next device in your network, and sending stuff to THAT device will travel as fast as possible, up to 100Mb/s (on paper -- reality is different, but no matter). A couple of tests that you can try out to try sorting the problem further would be to move stuff locally (e.g. you and another tech-savvy friend transfer a Debian ISO between the two computers) and see if the throughput stays consistent. Assuming you live in the dorms, the ideal test would be between two that are pretty far apart (e.g. on opposite sides of a courtyard/quad) so that you can traverse more network segments. You can also run traceroute to check how many hops it takes to get somewhere, and how responsive each hop is (e.g. from me to google it's 17 right now, with most hops taking 20-30 ms ... but there are two that are really bad -- one's 50ms and the other was 110). Most of the time you'll see things are fast, but if you check and see something that's taking 500ms to respond, it could be a problem. NOTE -- not all devices will be under the control of your network guys ... but you'll generally be able to see where the "inside" hits the "outside" because it'll go from 172.21.x.x to something else (e.g. 10.x.x.x). If you want to get to the real low-end stuff and dig out things, you can try wireshark ... but it's got a bit of a learning curve... -Dan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5319f03b.6050...@djph.net
