Can't kill process

Normally, this is the kind of thing that is a problem in a Windows environment. Fortunately, *nix provides for a switch that will do what the normal “kill” command won’t do on its own. I couldn’t get Hellanzb to stop running, so I ran “kill -9 process#” and it worked. Good thing to remember.

How to: Move a process to the background, when it's typing up the terminal

So, for instance, let’s say that you run top in the console. At that point, it will return a list of running processes. If you wanted to keep top running, but also use the console again, you can type CTRL + Z to get out of it, then type bg to “background” the process. If you’d like to bring top to the foreground again, type fg and top will return with its running processes. The only catch to this is, once you’ve exited out of that console, you can no longer bg or fg the process. Pretty handy tool.

cmdwatch

I asked Cade what command will show me a dynamic view of netstat. He told me that ‘cmdwatch’ in BSD (‘watch’ in Linux) will show me the dynamic status of any command. For instance, in BSD, cmdwatch -n 1 ‘netstat -an’ will refresh netstat every one second. Very handy and works on infinite commands.

Screen: Using Screen

Last night, I finally dug in a little, into what Screen is, what it does, and how I can use it. I learned the following:

screen -r will show you what screen sessions are available.
screen -S newname will create a new screen session, called something like newname.94394. Helps to keep track of multiple screens and what they are used for.

Once you’re in a screen session, you can view a split screen by hitting ctrl + a and S.
To move between the two screens, you hit ctrl + a and tab.

That’s it, for now!

Some Serious Server Policy Changes

In light of recent events (I lost a whole database at work, which was used for Helpdesk Documentation), it has become necessary (has been for some time) to make sure that all of the websites and servers that I use on a daily basis are backed up. This is going to take some effort, but will obviously be worth it, because this kind of thing happens at least yearly to me. So I will begin to document my thoughts on this.

1. Find out what version operating system FreeBSD:
2. What software and what versions
3.