How to Crash my FreeBSD server - run portsdb
So, in a vain attempt to upgrade Transmission I have utterly destroyed it instead. It's currently deinstalled, and when I try to install it from ports it get errors and when I try to install the package it downloads the tbz and just stops at that point.
So I figured I should try to learn more about updating ports, since obviously I blew it pretty badly. I was using the information here:
to try and get everything up-to-date. Well, the issue I have is that when I run the portsbd -Uu command, it locks up my system. I'm not sure exactly at what point, it does start the process. I haven't done it from the console, just a SSH session from work. At some point after I issue the command and it starts the process, I lose all connectivity, and when I get home the box is unresponsive and I have nothing (no display, can't get Num Lock key to light on/off, etc.) and I have to power down manually.
So, I'm curious about how I've managed to destroy the Transmission port so effectively, and of course how I am breaking my machine by running portsdb. Are there specific log files to look into to dig a little deeper on this stuff?
|Thread||Thread Starter||Forum||Replies||Last Post|
|fluxbox crash? HELP||bsdnewbie999||OpenBSD General||9||2nd April 2009 05:35 AM|
|Firefox 2.0 Crash Problem||disappearedng||FreeBSD General||13||8th November 2008 05:54 AM|
|Java + FF3 = crash||graudeejs||FreeBSD Ports and Packages||12||3rd August 2008 09:26 AM|
|portsdb -Uu failes at ismail, BUG w/ fix||blancolado||FreeBSD Ports and Packages||4||21st July 2008 08:54 PM|
|Kde crash refuse to load due to splash change||whispersGhost||Solaris||8||12th June 2008 12:40 PM|